Repository navigation
Release pm-beads v2026.10.09 - #135
Conversation
|
PR author is in the excluded authors list. |
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis release-only PR updates pm-beads from version 2026.10.5 to 2026.10.9 across runtime and package metadata; no functional behavior changes are included. Reviewers should verify that all version fields are synchronized and that the protected-PR release workflow will publish and tag only after merge. 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-beads",
- "version": "2026.10.5",
+ "version": "2026.10.9",
"description": "Beads JSONL importer/exporter. Import work items from the Beads JSONL format into pm and export pm items back to Beads JSONL, preserving ids and dependency edges.",
"author": "@unbraind",
</code_context>
<issue_to_address>
**Release changelog remains stale**
When this pull request runs CI with package version `2026.10.9`, `npm run changelog:check` renders the changelog using the package version, but `CHANGELOG.md` still starts at `2026.10.5`; the generated output differs and CI fails.
Regenerate and include `CHANGELOG.md` for version `2026.10.9`.
</issue_to_address>Sourcery assessment
Needs a human reviewer. 1 finding to address first, and if the version is wrong, the released package and extension metadata could be published under an incorrect version, and reverting the source would not undo an already-published release. The problem is bounded and can be corrected with a subsequent release or metadata fix.
Blocking findings: package.json:3
Automated daily release metadata for
v2026.10.09. 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:
Summary by cubic
Publishes release v2026.10.09 of
pm-beadsby bumping the version from 2026.10.5 to 2026.10.9 acrossindex.ts,manifest.json,package.json, andpackage-lock.json. The release gate already passed; npm publication and tagging stay blocked until this PR is merged.Written for commit 34f2b03. Summary will update on new commits.