fix(ci): point Dependabot at the pnpm workspace root - #71
Merged
Conversation
The npm entry aimed at /apps/web updated only apps/web/package.json and left the root pnpm-lock.yaml untouched, so every resulting PR failed CI on ERR_PNPM_OUTDATED_LOCKFILE — even a postcss patch bump (#69). A pnpm workspace has one lockfile at the root, so a single npm entry there covers both apps and keeps the lockfile in step; the root entry produced correct PRs (#66 updated the manifest and the lockfile together). Also folds the former root entry's schedule into the single npm entry and adds an eslint group.
This was referenced Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dependabot opened 13 PRs within minutes of #55 merging, and every npm one for
apps/webfailed CI — including a postcss patch bump (#69). That was my configuration bug, not a bad dependency.Root cause
A pnpm workspace has one
pnpm-lock.yamlat the root. My config declared an npm entry withdirectory: /apps/web, so Dependabot editedapps/web/package.jsonand left the root lockfile untouched:The contrast is visible in the PR file lists:
directory: /apps/headless/package.json+pnpm-lock.yamldirectory: /apps/webapps/web/package.jsononlyFix
One npm entry at
/covering the whole workspace, with the grouping rules kept (react, next, tailwind, types, plus a new eslint group). The comment in the file explains why, so nobody re-splits it later.Follow-up
The seven malformed PRs (#62–#65, #67–#69) will be closed; Dependabot regenerates them correctly against the root on the next run. Note that CI does not exercise
release.yml, so thedownload-artifactandgh-releasebumps (#57, #58) are not validated by a green check — those need a tag run or manual review before merging.