Skip to content

ci(release): bump the rc number automatically instead of pinning release-as - #279

Merged
jfcmartins merged 1 commit into
mainfrom
ci/release-please-rc-versioning
Nov 6, 2026
Merged

jfcmartins merged 1 commit into
mainfrom
ci/release-please-rc-versioning

Conversation

@jfcmartins

Copy link
Copy Markdown
Collaborator

What and why

The release PR kept proposing 0.1.0-rc.2 after rc.2 shipped, because release-as was still set in release-please-config.json. That setting forces the version.

This drops release-as and sets versioning: prerelease with prerelease-type: rc, so the next release PR bumps the rc number by itself (rc.3, rc.4, ...). The runbook and ADR-0024 now say release-as is a one-release override to remove right after it ships, and how to go from rc to a final version.

Related: ADR-0024. The stale release PR #276 should be rewritten by release-please after merge.

How it was verified

  • release-please-config.json parses as JSON.
  • unverified: not run against release-please. The rc.N bump comes from its documented prerelease strategy, not from observation.

Not verified

What release-please proposes on main after merge (expect 0.1.0-rc.3, not 0.2.0). If it is wrong, set release-as for that one release.

Checklist

  • n/a Tests, fmt, clippy (no Rust changes)
  • Docs updated (runbook, ADR-0024)
  • n/a Phase work
  • Secrets, mTLS, audit untouched
  • n/a New dependency
  • n/a New entry point or data store
  • Commits are conventional, small and focused

Compatibility and rollback

Release tooling config only. Revert to roll back; set release-as to force a version.

@jfcmartins
jfcmartins marked this pull request as ready for review November 6, 2026 19:40
@jfcmartins
jfcmartins merged commit 334a207 into main Nov 6, 2026
12 checks passed
@jfcmartins
jfcmartins deleted the ci/release-please-rc-versioning branch November 6, 2026 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant