fix: harden release attestation pipeline

[hatayama]

Background

A runner release published assets whose attestation digest did not match its tag commit. The dispatcher correctly rejected that release, but the mismatch was not caught before publication and a package release could still pin it.

Changes

• Verify every remote runner asset and attached Sigstore bundle against the release tag before publishing a draft release.
• Block package-release synchronization unless every required runner asset attests to the runner release tag.
• Make roll-forward the documented recovery path and remove the unusable historical recovery-target publish mode.
• Keep release publication pinned to the approved event commit, including tag-SHA rechecks.

Verification

• Native publish workflow and release-target resolver shell tests
• Package-release synchronization test harness
• POSIX shell syntax checks and workflow YAML parsing
• CodeRabbit and advisor reviews for PRs fix: Block releases with mismatched attestation digests #1819, fix: Block package releases with invalid runner attestations #1820, docs: Guide release recovery through roll-forward #1821, and fix: remove invalid recovery-target release path #1822

The CI run for this PR must pass, including Windows, before merge.

[coderabbitai]

Warning

Review limit reached

@hatayama, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8014be3a-ecff-47eb-9afa-87d9ebb11fb8

📥 Commits

Reviewing files that changed from the base of the PR and between c772112 and f4d2087.

📒 Files selected for processing (7)

• .github/workflows/native-cli-publish.yml
• docs/release-recovery-runbook.md
• scripts/resolve-native-cli-release-target.sh
• scripts/sync-release-please-package-releases.sh
• scripts/test-native-cli-publish-workflow.sh
• scripts/test-resolve-native-cli-release-target.sh
• scripts/test-sync-release-please-package-releases.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/release-pipeline-hardening-integration

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}