chore(deps): adopt pm-cli 2026.7.28 by unbraind · Pull Request #19 · unbraind/pm-github

unbraind · 2026-07-28T03:36:41Z

Bumps @unbrained/pm-cli from ^2026.7.27 to ^2026.7.28 (devDependencies) and >=2026.7.27 to >=2026.7.28 (peerDependencies), and the package version to 2026.7.28 across package.json, manifest.json, and index.ts.

Changes:

@unbrained/pm-cli ^2026.7.27 → ^2026.7.28 in devDependencies
@unbrained/pm-cli >=2026.7.27 → >=2026.7.28 in peerDependencies
Package version 2026.7.27 → 2026.7.28 in package.json, manifest.json, and index.ts
Regenerated CHANGELOG.md via changelog:full
Updated .gitattributes merge-driver pattern per the 2026.7.28 prepare hook

npm run release:check passes (typecheck, build, test, audit, pack dry-run, changelog check).

pm item: https://github.com/unbraind/pm-github/blob/main/.agents/pm/chores/pm-github-b646.toon

Summary by cubic

Adopts @unbrained/pm-cli 2026.7.28 and bumps the extension version to 2026.7.28. Updates @unbrained/pm-cli dev/peer ranges, regenerates CHANGELOG.md after closing the item to fix changelog check, widens .gitattributes merge-driver to .agents/pm/**/*.json, and adds a correction note in the pm item history about the earlier release check claim.

^{Written for commit e792af4. Summary will update on new commits.}

Bump @unbrained/pm-cli from ^2026.7.27 to ^2026.7.28 in devDependencies and >=2026.7.27 to >=2026.7.28 in peerDependencies; bump package version to 2026.7.28 in package.json, manifest.json, and the version constant in index.ts. Regenerate CHANGELOG via changelog:full. Update .gitattributes merge-driver pattern per the 2026.7.28 prepare hook.

gemini-code-assist · 2026-07-28T03:36:44Z

Caution

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

sourcery-ai

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 · 2026-07-28T03:36:57Z

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates this package and its pm-cli dependency to 2026.7.28, refreshes the changelog, adjusts git attributes per the new pm-cli prepare hook, and adds pm agent metadata/history files.

File-Level Changes

Change	Details	Files
Bump package and pm-cli versions to 2026.7.28 and sync metadata.	Update package version to 2026.7.28 in package.json, manifest.json, and index.ts to keep the extension’s declared version consistent across build, runtime, and distribution metadata. Raise @unbrained/pm-cli peerDependency floor from >=2026.7.27 to >=2026.7.28 and devDependency range from ^2026.7.27 to ^2026.7.28 to align with the new CLI release. Regenerate CHANGELOG.md so the previous Unreleased section becomes a tagged 2026.7.28 entry dated 2026-07-28. Update .gitattributes merge-driver pattern according to the pm-cli 2026.7.28 prepare hook so pm-specific files resolve correctly in merges. Add/update .agents/pm chore and history artifacts for pm-github-b646, and refresh package-lock.json to reflect the new dependency version graph.	`package.json` `manifest.json` `index.ts` `CHANGELOG.md` `.gitattributes` `.agents/pm/chores/pm-github-b646.toon` `.agents/pm/history/pm-github-b646.jsonl` `package-lock.json`

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

Contact our support team for questions or feedback.
Visit our documentation for detailed guides and information.
Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

coderabbitai · 2026-07-28T03:36:58Z

Walkthrough

The extension and package versions were bumped to 2026.7.28, pm-cli compatibility constraints were updated, the changelog was dated, PM release records were added, and the pm-json merge pattern was broadened.

Changes

Release update

Layer / File(s)	Summary
Version and compatibility updates `package.json`, `manifest.json`, `index.ts`	Package, manifest, and extension versions changed to `2026.7.28`; `@unbrained/pm-cli` peer and development requirements were updated accordingly.
Release records and changelog `CHANGELOG.md`, `.agents/pm/chores/...`, `.agents/pm/history/...`, `.gitattributes`	The changelog and PM records document the release, while the `pm-json` merge driver now applies to all PM JSON files.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 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.28.
Description check	✅ Passed	The description accurately matches the version bumps, changelog regeneration, and .gitattributes update.

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch chore/adopt-pm-cli-2026-7-28

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 · 2026-07-28T03:38:09Z

Greptile Summary

This PR adopts @unbrained/pm-cli 2026.7.28, bumping the extension version from 2026.7.27 to 2026.7.28 consistently across package.json, manifest.json, index.ts, and package-lock.json. It also widens the .gitattributes pm-json merge-driver pattern and regenerates CHANGELOG.md after correctly closing the tracking item.

Version 2026.7.28 applied uniformly across all four version-bearing files; pm-cli dev and peer ranges updated in sync.
Transitive dependency @toon-format/toon moves from 2.3.1 to 4.1.0 (pulled in by the new pm-cli release); this is lock-file-resolved and confined to devDependencies.
The PM tracking item (pm-github-b646) documents a self-corrected ordering issue (changelog generated before item close) with an append-only correction note, and the final CHANGELOG.md includes the entry.

Confidence Score: 5/5

Safe to merge — a mechanical version bump with no logic changes, consistent version strings across all files, and a self-documented correction to the changelog ordering process.

All four version-bearing files (package.json, package-lock.json, manifest.json, index.ts) are updated consistently. The pm-cli and toon dependency upgrades are straightforward and lock-file-pinned. The .gitattributes widening is intentional and scoped to the .agents/pm/ tree. The CHANGELOG now correctly includes the chore item's own entry after the ordering fix was applied.

Files Needing Attention: No files require special attention.

Important Files Changed

Filename	Overview
package.json	Version bumped from 2026.7.27 to 2026.7.28; pm-cli dev/peer ranges updated consistently
package-lock.json	Lock file regenerated; resolves pm-cli 2026.7.28 and upgrades transitive dep @toon-format/toon from 2.3.1 to 4.1.0
manifest.json	Version field updated from 2026.7.27 to 2026.7.28, consistent with package.json
index.ts	Version constant updated from 2026.7.27 to 2026.7.28 in the extension definition
.gitattributes	Merge-driver pattern widened from .agents/pm/schema/.json to .agents/pm//.json per 2026.7.28 prepare hook
CHANGELOG.md	Unreleased section promoted to 2026.7.28 release entry with the adoption chore item added after close
.agents/pm/chores/pm-github-b646.toon	New PM chore item tracking the adoption; includes a correction note documenting the changelog ordering fix
.agents/pm/history/pm-github-b646.jsonl	Append-only audit history for the pm chore item with create, close, and correction note operations

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[pm-cli 2026.7.28 released] --> B[Bump devDependency\n^2026.7.27 → ^2026.7.28]
    A --> C[Bump peerDependency\n>=2026.7.27 → >=2026.7.28]
    B --> D[npm install resolves\npm-cli 2026.7.28\n+ toon 2.3.1 → 4.1.0]
    D --> E[package-lock.json updated]
    C --> F[package.json peerDeps updated]
    B --> F
    F --> G[Bump package version\n2026.7.27 → 2026.7.28]
    G --> H[package.json]
    G --> I[manifest.json]
    G --> J[index.ts version constant]
    G --> K[Close PM chore item\npm-github-b646]
    K --> L[Regenerate CHANGELOG.md\nafter close]
    L --> M[Unreleased → 2026.7.28\nwith b646 entry included]
    M --> N[release:check passes\ntypecheck, build, test,\naudit, pack, changelog]

_{Reviews (6): Last reviewed commit: "docs(pm): record that the close reason o..." | Re-trigger Greptile}

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CHANGELOG.md`:
- Line 3: The release artifacts incorrectly record 2026.7.28 as complete while
changelog validation fails. Regenerate CHANGELOG.md so the 2026.7.28 section
matches PM records, then run release:check and update the close reason in
.agents/pm/chores/pm-github-b646.toon and the corresponding historical close
event in .agents/pm/history/pm-github-b646.jsonl only after validation passes.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 1beae2de-a331-4ed5-8a43-4a251b328551

📥 Commits

Reviewing files that changed from the base of the PR and between 295534f and 1ec94fd.

⛔ Files ignored due to path filters (1)

package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (7)

.agents/pm/chores/pm-github-b646.toon
.agents/pm/history/pm-github-b646.jsonl
.gitattributes
CHANGELOG.md
index.ts
manifest.json
package.json

The changelog was generated before the pm item for this change was closed, so the committed CHANGELOG.md was missing the item's own entry and changelog:check failed in CI while passing locally against the stale file. Where .gitattributes also changed, that is the 2026.7.28 prepare hook widening the merge fence from .agents/pm/schema/*.json to .agents/pm/**/*.json so tracked non-item JSON no longer line-conflicts between agents on different branches.

…heck The item's close reason asserted release:check passed when it had not: the changelog was generated before the item was closed, so CHANGELOG.md was missing the item's own entry and changelog:check failed in CI while passing locally against the stale file. Add a correction note rather than rewriting the close reason. Item history is append-only and an audited tracker should show the correction, not hide it.

sourcery-ai Bot reviewed Jul 28, 2026

View reviewed changes

coderabbitai Bot reviewed Jul 28, 2026

View reviewed changes

Comment thread CHANGELOG.md

unbraind added 2 commits July 28, 2026 06:01

unbraind merged commit f9adfc8 into main Jul 28, 2026
6 checks passed

unbraind deleted the chore/adopt-pm-cli-2026-7-28 branch July 28, 2026 04:43

coderabbitai Bot mentioned this pull request Jul 29, 2026

Adopt pm-cli 2026.7.29 #23

Merged

coderabbitai Bot mentioned this pull request Aug 6, 2026

Gate CI on durable PM tracker health with pm 2026.8.6 #29

Merged

coderabbitai Bot mentioned this pull request Aug 16, 2026

Declare the pm CLI floor in the field the CLI actually enforces #43

Merged

Navigation Menu

chore(deps): adopt pm-cli 2026.7.28 - #19

chore(deps): adopt pm-cli 2026.7.28#19
unbraind merged 3 commits into
mainfrom
chore/adopt-pm-cli-2026-7-28

unbraind commented Jul 28, 2026 •

edited by cubic-dev-ai Bot

Loading

Uh oh!

gemini-code-assist Bot commented Jul 28, 2026

Uh oh!

sourcery-ai Bot left a comment

Uh oh!

sourcery-ai Bot commented Jul 28, 2026

Reviewer's Guide

File-Level Changes

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

coderabbitai Bot commented Jul 28, 2026 •

edited

Loading

Uh oh!

greptile-apps Bot commented Jul 28, 2026 •

edited

Loading

Important Files Changed

Flowchart

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

unbraind commented Jul 28, 2026 • edited by cubic-dev-ai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by cubic

Uh oh!

gemini-code-assist Bot commented Jul 28, 2026

Uh oh!

sourcery-ai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

sourcery-ai Bot commented Jul 28, 2026

Reviewer's Guide

File-Level Changes

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

coderabbitai Bot commented Jul 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

greptile-apps Bot commented Jul 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 5/5

Important Files Changed

Flowchart

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

unbraind commented Jul 28, 2026 •

edited by cubic-dev-ai Bot

Loading

coderabbitai Bot commented Jul 28, 2026 •

edited

Loading

greptile-apps Bot commented Jul 28, 2026 •

edited

Loading