Skip to content

Configure Dependabot and relax exact pnpm overrides - #2442

Open
mbiernacik wants to merge 2 commits into
mainfrom
pnpm-dependabot-config
Open

mbiernacik wants to merge 2 commits into
mainfrom
pnpm-dependabot-config

Conversation

@mbiernacik

Copy link
Copy Markdown
Contributor

Problem

Since the move to pnpm, every Dependabot security update job fails with security_update_not_possible and Dependabot hasn't opened a PR. With pnpm, Dependabot can only update direct dependencies, and all current alerts are for transitive ones. Those are fixed by hand with pnpm.overrides, but several overrides pin exact versions, so even compatible patch releases need an edit of the override.

Changes

  • packageManager: pnpm@9.7.1 in package.json, the version Bazel uses. Without it, Dependabot guesses pnpm 10.
  • .github/dependabot.yml: security updates only (open-pull-requests-limit: 0 disables version updates), grouped into a single PR.
  • Ranges instead of exact versions in pnpm.overrides where the pinned version is within the range requested by every package that depends on it: fast-uri, mdurl, @eslint-community/eslint-utils, @eslint/plugin-kit. Overrides that intentionally force a version outside the requested range (e.g. brace-expansion, serialize-javascript, uuid) are unchanged. Resolved versions don't change; only the overrides section of pnpm-lock.yaml does.
  • contributing.md: new package versions reach the CI registry with a delay, so add or update dependencies with that registry if you have access; how to update transitive dependencies with overrides, and when to use a range or an exact version.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants