ci(release): prepare coordinated versions through Actions - #39
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release preparation currently requires editing coordinated Cargo versions by hand. Add a
Prepare releaseActions workflow that accepts a stable target version, promotes the reviewedUnreleasednotes, and opens a release PR with matching workspace, internal dependency, and lockfile versions. Existing tag builds, draft review, and public distribution remain the release path.The Rust preparer preserves manifest formatting and third-party lock entries, leaves independently versioned test packages intact, rejects invalid/reused versions or missing notes, and restores its inputs if validation fails. The workflow reuses identical release proposals and refuses to overwrite differing branches. It uses the existing release credential so normal PR CI runs.
Validation: release helper tests (13 passed), strict helper Clippy, workspace formatting, workflow YAML/Bash syntax, and diff checks passed. An isolated run against the actual current workspace prepared 0.4.0 successfully, passed the existing tag/inventory validator and locked Cargo metadata, and changed only the three intended release files. No package version is changed in this PR; Actions will produce the version PR after merge.