The version-only comparison blanked the whole launch argument, so a release
that swapped rea-agents for another package passed the notes check as a
version bump. Mask only the version after the last "@" and test a changed
package name.
The plugin readiness command in the installation guide now uses the pinned
release version, so its report describes the server the plugin starts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The publication history check admitted the plugin manifests whole, so a
release could change plugin behavior, such as the bundled skill path or the
server environment, and still pass as release-only. Compare each manifest
across the release with its version and pinned server launch blanked, and
treat any other difference as a product change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Release PRs now bump .claude-plugin/plugin.json and .codex-plugin/plugin.json,
but the publication history check rejected them as post-notes product
changes and the release configuration test still expected the previous
extra-files list. Admit both manifests in the release-only allowlist, expect
them in the Release Please configuration, and assert that each manifest
version matches package.json.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
morluto
GamerDubz