Skip to content

Adopt pm-cli 2026.7.29 - #23

Merged
unbraind merged 1 commit into
mainfrom
adopt-pm-cli-2026-7-29
Jul 29, 2026
Merged

Adopt pm-cli 2026.7.29#23
unbraind merged 1 commit into
mainfrom
adopt-pm-cli-2026-7-29

Conversation

@unbraind

@unbraind unbraind commented Jul 29, 2026

Copy link
Copy Markdown
Owner

Summary

Bumps the pm-cli dependency to 2026.7.29 and audits for breaking changes and fixed upstream workarounds.

Changes

  • Dependency bump: @unbrained/pm-cli devDependency → 2026.7.29, peerDependency → >=2026.7.29
  • --all flag audit: No hits found. The removed pm list --all flag is not referenced anywhere in source, docs, or CI.
  • Upstream workaround audit: None applicable.
    • GH-651 (signed activity window): no hits
    • GH-672 (context low_level blocked state): blocked references are this package's own link-deps feature, not pm context workarounds
    • GH-676 (list --tag CSV): package uses --tags on pm create/update (tag mutations) but never calls pm list --tag
    • GH-785/792 (pm health runtime dirs): no hits
    • GH-794 (output_format override): no hits

Quality gates

  • npm run check (typecheck): ✅ pass
  • npm 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 date
  • npm run audit:prod: ✅ 0 vulnerabilities

pm tracking item

- 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
@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @unbraind, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

@sourcery-ai

sourcery-ai Bot commented Jul 29, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Bumps 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

Change Details Files
Update pm-cli dependency version requirements to 2026.7.29.
  • Raise peer dependency range for @unbrained/pm-cli from >=2026.7.28 to >=2026.7.29.
  • Raise dev dependency range for @unbrained/pm-cli from ^2026.7.28 to ^2026.7.29.
  • Regenerate package-lock.json to reflect the new pm-cli version.
package.json
package-lock.json
Document the pm-cli adoption and coverage gate behavior in changelog and PM agent artifacts.
  • Add an Unreleased changelog section describing the new coverage gate enforcement and pm-cli adoption.
  • Add a PM chore descriptor for the pm-cli 2026.7.29 adoption.
  • Add a PM history log entry for the pm-cli 2026.7.29 adoption.
CHANGELOG.md
.agents/pm/chores/pm-github-801z.toon
.agents/pm/history/pm-github-801z.jsonl

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Review Change Stack

Walkthrough

The repository updates @unbrained/pm-cli requirements to 2026.7.29, adds unreleased changelog entries, and records the dependency audit and completed maintenance task lifecycle.

Changes

pm-cli adoption

Layer / File(s) Summary
Version and release records
package.json, CHANGELOG.md
Updates peer and development dependency requirements to 2026.7.29 and documents the adoption and coverage-gate entry under Unreleased.
Maintenance tracking
.agents/pm/chores/*, .agents/pm/history/*
Adds chore metadata and lifecycle records covering the dependency update, repository audits, quality-gate results, and closure status.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly summarizes the main change: adopting pm-cli 2026.7.29.
Description check ✅ Passed The description matches the dependency bump and audit/quality-gate work shown in the changes.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch adopt-pm-cli-2026-7-29

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@greptile-apps

greptile-apps Bot commented Jul 29, 2026

Copy link
Copy Markdown

Greptile Summary

Bumps @unbrained/pm-cli to 2026.7.29 and records the chore.

  • Raises devDependency (^2026.7.29) and peerDependency (>=2026.7.29) in package.json / lockfile.
  • Adds Unreleased changelog notes (pm-cli adopt + a coverage-gate entry).
  • Adds closed pm chore tracking (pm-github-801z toon + history).

Confidence Score: 5/5

This 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.

Important Files Changed

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

@unbraind

Copy link
Copy Markdown
Owner Author

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 adopt-pm-cli-2026-7-29, so a finding that applies here almost certainly applies to the other 17 — please say so explicitly when you spot one, as that is how the fleet-wide fixes in this wave were found.

What the audit actually covered, and why no source changed here. 2026.7.29 has exactly one breaking change: pm list --all was removed (GH-793) in favour of explicit pm list-all / list-open / list-in-progress / list-blocked / list-closed / list-canceled / list-draft subcommands, with pm list --status <s> retained. A fleet-wide grep found zero references in any source, doc, README or workflow. Six upstream fixes were also checked for now-obsolete local workarounds (pm activity bare relative windows, pm context blocked-state rows, pm list --tag CSV shape, fresh-clone pm health semantics, and the destructive identity output_format override) — none of this package's code existed to work around them, so nothing was removed.

Two things NOT to flag here. A service override that returns the same ctx.payload reference to decline is the correct contract and must stay — GH-794 made a copied identity override inert, it did not make declining unnecessary. And --all-release-tags (pm-changelog) and --atomic (pm-csv/pm-jira) are our own packages' flags, unrelated to the removed host flag; a bare flag name is genuinely ambiguous in this ecosystem, so the command-qualified form is what any audit record should use.

Defects this wave's reviews caught, for calibration: an unbounded >= range written into runtime dependencies (correct only for peerDependencies), three READMEs advertising a pm-cli >=2026.7.5 floor that contradicted the new peer floor, two pm audit records describing a broader scope than was verified, and in pm-changelog a release-pinned provenance skew, a sample ordering that contradicted its own documented contract, a no-signal item mislabelled as a created_at fallback, and an unsound SDK cast that led to a genuine upstream type bug (pm-cli#808). Three upstream issues were filed from testing the new surfaces: #805, #806, #807.

Gates on this PR are green on Node 22 and 26, the coverage ratchet holds, audit:prod is clean, and changelog:check reports up to date.

@unbraind
unbraind merged commit a8809b9 into main Jul 29, 2026
7 checks passed
@unbraind
unbraind deleted the adopt-pm-cli-2026-7-29 branch July 29, 2026 05:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant