ci: upload artifacts to draft releases

[robjtede]

Summary

• move the release asset build matrix into the release workflow
• upload archives and SHA-256 checksums to the release-plz draft release
• generate build provenance attestations before publication
• remove the post-publication deployment workflow
• use protobug-vX.Y.Z tags for protobug releases

Why

Immutable releases cannot be modified after publication. The previous workflow only built and uploaded binaries after the release was published, so enabling release immutability would prevent those assets from being attached.

The release-plz configuration already creates draft releases. This change follows the inspect-cert-chain release flow by passing the created release tag into a dependent asset-upload job and explicitly targeting that tag.

Impact

Release binaries, checksums, and attestations will be present on the draft release before a maintainer publishes it. Once this lands, repository release immutability can be enabled safely.

Validation

• prettier --check .github/workflows/release.yml
• parsed .github/workflows/release.yml with Ruby YAML
• git diff --check
• nix develop -c just check

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 30 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8773f2cd-bd48-4094-a80a-b1c0752934ca

📥 Commits

Reviewing files that changed from the base of the PR and between 3b6ac2f and 548739f.

📒 Files selected for processing (3)

• .github/workflows/deploy.yml
• .github/workflows/release.yml
• .release-plz.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch agent/immutable-releases

---

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.}