Repository navigation
Keep pm packages in the pm-toolchain Dependabot group - #120
Conversation
After #118 Dependabot put pm-ops into the generic dependencies group, where it was capped at 2026.9.29 by itself instead of moving with @unbrained/pm-cli. The dependencies group now excludes the pm-toolchain patterns so the groups are disjoint. Closes pm-v1it with the auto-merge proof from #119. pm item: pm-v1it
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThe PR prevents Dependabot from placing @unbrained/pm-cli or pm-* packages in the generic dependencies group, keeping the PM toolchain updates together, and records the task closure and evidence that the prior auto-merge workflow works. Flow diagram for Dependabot package groupingflowchart LR
Updates[Dependabot updates]
PM[pm-toolchain group]
Generic[dependencies group]
Merge[Auto-merge workflow]
Updates -->|"@unbrained/pm-cli or pm-*"| PM
Updates -->|other packages| Generic
PM --> Merge
Generic --> Merge
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
…sions Review feedback: an update that fetch-metadata cannot classify must not auto-merge, so the condition now requires semver-minor or semver-patch outside the calendar-versioned pm-toolchain group. The job's write scopes are documented, the dependencies group selects every package explicitly, and the item's acceptance criteria name the pm-toolchain exception. pm item: pm-v1it
|
@coderabbitai full review |
Rate Limit Exceeded
|
|
@greptileai review |
Rate Limit Exceeded
|
What
dependenciesgroup now hasexclude-patterns: ["@unbrained/pm-cli", "pm-*"], so it is disjoint frompm-toolchain.Why
After #118 merged, Dependabot regrouped the open updates into #119 and put
pm-ops(2026.9.28 → 2026.9.29) into the genericdependenciesgroup instead ofpm-toolchain. pm packages must move together (pm-ops's newer releases expect a newer@unbrained/pm-cli), so they may only ever be bumped inpm-toolchain.Evidence that #118 works
dependabot-auto-mergeenabled squash auto-merge on it (run succeeded ondependabot/npm_and_yarn/dependencies-852671bb2a).pm item
Summary by Sourcery
Keep pm packages synchronized by making Dependabot groups disjoint and tightening automatic merge eligibility for other dependency updates.
Enhancements:
CI:
Summary by cubic
Keeps pm packages out of the generic
dependenciesDependabot group so they can only be bumped together inpm-toolchain.After #118, Dependabot routed
pm-opsintodependencies, where it was capped at 2026.9.29 instead of moving in sync with new@unbrained/pm-clireleases. Thedependenciesgroup now explicitly selects every npm package except thepm-toolchainpatterns (@unbrained/pm-cli,pm-*), making the two groups disjoint. The auto-merge workflow also now requires updates outsidepm-toolchainto be explicitly classified as minor or patch, so an unclassified or major update waits for a person.Written for commit 0198f54. Summary will update on new commits.