Repository navigation
ci: avoid duplicate Dependabot npm PRs in pnpm workspace - #147
Merged
Merged
Conversation
Dependabot was configured with both `/` and `/plugins/*` directories for the npm ecosystem. In a pnpm workspace with a shared root catalog and lockfile, this produced two PRs for the same group update, and the second one always ended up with merge conflicts. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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.
Summary
Limits the Dependabot
npmupdater to the root directory (/) only. Before, it was set to both/and/plugins/*.Why
This repo is a pnpm workspace with a single
pnpm-lock.yaml. All shared dev dependencies (rollup,@rollup/*,@babel/*, ...) are set in the rootpnpm-workspace.yamlcatalog, and the plugins reference them with"catalog:".Because both
/and/plugins/*were configured, Dependabot ran overlapping jobs and opened two PRs for the same group update on the same day:Both edit the same
pnpm-lock.yamlandpnpm-workspace.yaml. Once the first PR merges, the second has merge conflicts and stays stuck while Dependabot tries to rebase it (#145 is in that state now).Starting from the root, Dependabot should still pick up the
plugins/*packages and the shared catalog, so each group should get a single PR.Follow-up