Repository navigation
Release pm-graph v2026.10.04 - #123
Conversation
|
PR author is in the excluded authors list. |
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis automated release PR updates pm-graph from 2026.9.26 to 2026.10.04 in the source, distribution bundle, and package metadata; no functional behavior changes are included. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
There was a problem hiding this comment.
Hey - I've found 1 issue
Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments
### Comment 1
<location path="package.json" line_range="3" />
<code_context>
{
"name": "pm-graph",
- "version": "2026.9.26",
+ "version": "2026.10.4",
"description": "Knowledge graph and dependency graph extension for pm CLI workspaces, with optional Neo4j sync.",
"entry": "./dist/index.js",
</code_context>
<issue_to_address>
**issue:** The package version is bumped to 2026.10.4 while CHANGELOG.md still starts at 2026.9.26; the release checks regenerate the changelog from the package version and reject this stale file, blocking the protected release PR.
**Suggested fix:** Regenerate and commit CHANGELOG.md for version 2026.10.4 before merging.
</issue_to_address>Sourcery assessment
Needs a human reviewer. 1 finding to address first, and if the version is wrong, the package metadata and runtime-reported version could be published under an incorrect release identity; reverting the commit would not undo an already published artifact. The impact is bounded and can be corrected with a subsequent release.
Blocking findings: package.json:3
Automated daily release metadata for
v2026.10.04. The release gate passed before this PR was created; npm publication and tagging remain blocked until this protected PR is merged.Summary by Sourcery
Build: