Problem
The PR template requires:
and, two lines earlier:
These conflict. Bumping plugins/agent-collab/.claude-plugin/plugin.json requires check_release_consistency.py to also see the version move in the Codex manifest, marketplace.json metadata, the root README whatsnew line, the root README summary line, the licensing entry, and the generated CHANGELOG.md. The last of those is reserved to release PRs by the line above, so a content PR cannot satisfy both.
Reproduction
On a content PR, bumping both manifests to 4.6.0 and regenerating:
FAIL licensing: changelog licensing entry is missing 'agent-collab 4.6.0'
FAIL marketplace.json: metadata.version is 4.5.4, expected 4.6.0
FAIL CHANGELOG.md topmost header and changelog.d fragments do not mention 'agent-collab 4.6.0'
FAIL root README.md: whatsnew version is 4.5.4, expected 4.6.0
FAIL root README.md: summary line for 'agent-collab' at version 'v4.6.0' not found
RESULT: FAIL - release-version drift detected
12 tests go red. Reverting the bump restores green.
Why it matters
The checkbox reads as an obligation, so an author either leaves it unchecked without explanation, or attempts the bump and lands a red PR. Encountered on #77, where the bump was deferred to the release cut and the reason documented in the PR body.
Suggested resolution
Either scope the checkbox to release PRs explicitly, or state that version metadata is bumped by cut_release.py and not per-PR. No behaviour change implied; this is a template-accuracy fix.
Filed as a follow-up from #77 rather than fixed there, to keep that PR's scope to the change it declares.
Problem
The PR template requires:
and, two lines earlier:
These conflict. Bumping
plugins/agent-collab/.claude-plugin/plugin.jsonrequirescheck_release_consistency.pyto also see the version move in the Codex manifest,marketplace.jsonmetadata, the root README whatsnew line, the root README summary line, the licensing entry, and the generatedCHANGELOG.md. The last of those is reserved to release PRs by the line above, so a content PR cannot satisfy both.Reproduction
On a content PR, bumping both manifests to
4.6.0and regenerating:12 tests go red. Reverting the bump restores green.
Why it matters
The checkbox reads as an obligation, so an author either leaves it unchecked without explanation, or attempts the bump and lands a red PR. Encountered on #77, where the bump was deferred to the release cut and the reason documented in the PR body.
Suggested resolution
Either scope the checkbox to release PRs explicitly, or state that version metadata is bumped by
cut_release.pyand not per-PR. No behaviour change implied; this is a template-accuracy fix.Filed as a follow-up from #77 rather than fixed there, to keep that PR's scope to the change it declares.