Adopt pm-cli 2026.7.29 - #23
Conversation
- Bump @unbrained/pm-cli devDependency to 2026.7.29 - Set peerDependency to >=2026.7.29 - Audit for removed 'list --all' flag: no hits found - Audit for fixed upstream workarounds (GH-651/672/676/785/792/794): none applicable - All quality gates pass: 172 tests, coverage thresholds met
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
Reviewer's guide (collapsed on small PRs)Reviewer's GuideBumps the @unbrained/pm-cli dependency to 2026.7.29 and records the change in project metadata and PM agent tracking files, with no code-level behavior changes in this package. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
WalkthroughThe repository updates Changespm-cli adoption
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Greptile SummaryBumps
Confidence Score: 5/5This PR appears safe to merge; it is a lockfile-backed dependency and metadata bump with no identified behavioral defects. Only version constraints, lockfile resolution, changelog, and pm tracking metadata change; no application logic or security boundary is altered.
|
| Filename | Overview |
|---|---|
| package.json | Bumps @unbrained/pm-cli dev and peer ranges from 2026.7.28 to 2026.7.29. |
| package-lock.json | Resolves @unbrained/pm-cli to 2026.7.29 with updated integrity hash. |
| CHANGELOG.md | Documents Unreleased pm-cli adopt chore (and an added coverage-gate note). |
| .agents/pm/chores/pm-github-801z.toon | Closed chore item documenting the bump and upstream-workaround audits. |
Reviews (1): Last reviewed commit: "Adopt pm-cli 2026.7.29" | Re-trigger Greptile
|
Review feedback acknowledged and every bot comment on this PR has been voted. Adding cross-PR context the reviewers here cannot see, since it changes what is and is not worth flagging on a change of this shape. This is 1 of 18 identical adoptions. pm-cli 2026.7.29 published today and closes nine issues this fleet filed upstream (GH-784, GH-785, GH-787, GH-792, GH-793, GH-794, GH-799, plus the root causes behind GH-651/672/675/676). Every public package in the fleet got the same treatment on a branch named What the audit actually covered, and why no source changed here. 2026.7.29 has exactly one breaking change: Two things NOT to flag here. A service override that returns the same Defects this wave's reviews caught, for calibration: an unbounded Gates on this PR are green on Node 22 and 26, the coverage ratchet holds, |
Summary
Bumps the pm-cli dependency to 2026.7.29 and audits for breaking changes and fixed upstream workarounds.
Changes
@unbrained/pm-clidevDependency →2026.7.29, peerDependency →>=2026.7.29--allflag audit: No hits found. The removedpm list --allflag is not referenced anywhere in source, docs, or CI.blockedreferences are this package's own link-deps feature, not pm context workarounds--tagson pm create/update (tag mutations) but never callspm list --tagQuality gates
npm run check(typecheck): ✅ passnpm run coverage: ✅ 172 tests pass, thresholds met (lines 76.72% / threshold 76, branches 79.55% / threshold 78, functions 75.74% / threshold 75)npm run changelog:check: ✅ up to datenpm run audit:prod: ✅ 0 vulnerabilitiespm tracking item