Repository navigation
Adopt pm-cli 2026.7.27 with a real activation proof - #47
Conversation
Raises the pm-cli peerDependency to >=2026.7.27 and the devDependency to ^2026.7.27, refreshes the lockfile, and bumps all THREE version sites: package.json, manifest.json, and the module's own self-reported version constant. Bumping only package.json leaves an installed extension reporting a stale version to the host and to `pm extension --manage` — a reviewer caught exactly that drift on the sibling pm-starter change. An activation proof is mandatory for this bump, not optional. 2026.7.27 hardened host-owned global flags, and a collision aborts command registration AT the offending command — dropping it and every later sibling, while `--help` still exits 0 with a misleading Commander arity error (upstream unbraind/pm-cli#772). A version edit alone would prove nothing. Verified on the real CLI with the built extension installed into a throwaway workspace: - install ok, no warnings - `pm linear --help` exits 0 and registers - host commands intact: `pm list --json` still valid - flag-collision audit: no host-owned global declared Gates: build, typecheck, check, 63 tests passing, changelog:full + changelog:check after `git fetch --tags --force`. pm items: - pm-linear-zntu (Chore) — pm-cli 2026.7.27 adoption
|
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 GuideUpdates the extension to require and develop against pm-cli 2026.7.27, refreshes the lockfile, aligns all internal version reporting, and records the change in project automation metadata and changelog. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
|
Warning Review limit reached
Next review available in: 20 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
✨ 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 SummaryUpdates the project’s pm-cli compatibility baseline.
Confidence Score: 5/5The PR appears safe to merge. No blocking failures remain.
 T-Rex LogsWhat T-Rex did
|
| Filename | Overview |
|---|---|
| package.json | Raises the pm-cli peer and development dependency constraints from 2026.7.26 to 2026.7.27. |
| package-lock.json | Synchronizes root dependency metadata and the resolved pm-cli package with version 2026.7.27. |
| .agents/pm/chores/pm-linear-zntu.toon | Records the completed adoption chore and explicitly corrects the earlier inaccurate three-site version-bump claim. |
| .agents/pm/history/pm-linear-zntu.jsonl | Preserves the chore lifecycle and the follow-up correction in append-only history. |
| CHANGELOG.md | Adds an Unreleased entry for adopting pm-cli 2026.7.27. |
Reviews (2): Last reviewed commit: "docs(pm): correct the version-site claim..." | Re-trigger Greptile
Greptile review flagged inaccurate work-item metadata, and it was right. The chore description claimed this change bumps all THREE version sites (package.json, manifest.json, and the module's self-reported version constant). For this package that is wrong: manifest.json and the module constant were ALREADY 2026.7.27 on main, bumped by the daily release, so this PR touches only package.json (the pm-cli dependency ranges plus the package version) and the lockfile. The three-site rule itself still holds — it is why the bump script rewrites all three whenever they differ. It simply had nothing to do here. The claim was carried over verbatim from the pm-starter change, where manifest.json and the module constant genuinely were stale and a reviewer caught the drift. Verified: git diff against origin/main touches neither manifest.json nor index.ts in this package.
Bot feedback triage — all four read, voted, answered@greptile-apps 👍 — the finding was correct and is fixed. The chore description claimed this Verified before correcting — Where the wrong claim came from is worth recording: it was carried over verbatim from Corrected on the chore item with a note rather than a silent edit, so the record shows both the @sourcery-ai 👍 — accurate summary of the dependency change. @coderabbitai 👎 — @gemini-code-assist 👎 — consumer Gemini Code Assist is sunset; all review activity has ceased. Note for future reviews of this repoThe |
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
Tip For best results, initiate chat on the files or code changes.
For future reviews, I’ll treat the pm tracker artifacts as CLI-managed records: I’ll flag unmatched 🐇🔍 ✏️ Learnings added
|
Summary
Adopts pm-cli 2026.7.27.
@unbrained/pm-clipeerDependencies>=2026.7.26→>=2026.7.27@unbrained/pm-clidevDependencies^2026.7.26→^2026.7.272026.7.27:package.json,manifest.json, and the module's own self-reportedversionconstantThat last point matters: bumping only
package.jsonleaves an installed extension reporting a staleversion to the host and to
pm extension --manage. A reviewer caught exactly that drift on thesibling pm-starter change, so it is handled up front here.
Why an activation proof is mandatory
2026.7.27 hardened host-owned global flags. A collision aborts command registration at the
offending command — dropping it and every later sibling — while
--helpstill exits 0 andinvoking the command yields a misleading Commander arity error that never mentions extensions
(pm-cli#772). A version edit on its own proves
nothing about whether the extension still works.
Verified on the real CLI, with the built extension installed into a throwaway workspace holding a
seeded item:
Gates
build,typecheck,check, 63 tests passing,changelog:full+changelog:checkafter
git fetch origin --tags --force(stale local release tags otherwise red the CI changelogcheck while passing locally).
pm items
pm-linear-zntu— Chore: pm-cli 2026.7.27 adoptionSummary by Sourcery
Adopt pm-cli version 2026.7.27 and record the upgrade in project metadata and automation artifacts.
Enhancements:
Documentation:
Chores:
Summary by cubic
Adopts
@unbrained/pm-cli2026.7.27 and includes a real activation proof under the new global-flag hardening. Verified on the CLI: clean install,pm linear --helpexits 0, host commands OK, no host-owned global collisions.@unbrained/pm-cli >=2026.7.27@unbrained/pm-cli ^2026.7.27manifest.jsonor module version changes; already at 2026.7.27Written for commit 06a6b05. Summary will update on new commits.