Tapico/node-posthog-openfeature

Dependency Dashboard

Closed this issue · 2 comments

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Pending Status Checks

These updates await pending status checks. To force their creation now, click the checkbox below.

  • chore(deps): update dependency @types/node to v20.13.0
  • chore(deps): update dependency eslint to v9.4.0

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

  • chore(deps): update renovatebot/github-action action to v40.1.11

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

Detected dependencies

asdf
.tool-versions
  • node 20.14.0
  • pnpm 8.15.8
github-actions
.github/workflows/build.yml
  • actions/checkout v4
  • pnpm/action-setup v3
  • actions/setup-node v4
  • actions/cache v4
  • actions/setup-node v4
.github/workflows/npm-publish.yml
  • actions/checkout v4
  • pnpm/action-setup v3
  • actions/setup-node v4
  • actions/cache v4
  • actions/checkout v4
  • pnpm/action-setup v3
  • actions/setup-node v4
  • actions/cache v4
  • google-github-actions/release-please-action v4
.github/workflows/renovatebot.yml
  • actions/checkout v4
  • renovatebot/github-action v40.1.9
.github/workflows/stale.yml
  • actions/stale v9
npm
example/package.json
  • @types/node ^20.12.7
  • typescript 5.4.5
package.json
  • @openfeature/core ^1.1.0
  • @openfeature/server-sdk ^1.13.4
  • @opentelemetry/api ^1.8.0
  • posthog-node ^4.0.0
  • @opentelemetry/api ^1.8.0
  • @types/jest ^29.5.12
  • @typescript-eslint/eslint-plugin ^7.6.0
  • @typescript-eslint/parser ^7.6.0
  • eslint 9.3.0
  • eslint-config-prettier ^9.1.0
  • jest ^29.7.0
  • jest-junit ^16.0.0
  • jest-serializer-path ^0.1.15
  • prettier ^3.2.5
  • ts-jest ^29.1.2
  • tsup ^8.0.2
  • typescript ^5.4.5
  • @opentelemetry/api ^1.8.0
  • node >=20.12.0

Oops! It looks like we lost track of this issue. What do we want to do here? This issue will auto-close in 7 days without an update.

This issue was auto-closed due to inactivity. While we wish we could keep responding to every issue, we unfortunately don't have the bandwidth and need to focus on high-value issues.