Repository navigation
Create a release when a tag is pushed on main - #13
Merged
Merged
Conversation
The release workflow ran only after someone created a GitHub release by hand. It now runs when a tag that starts with v is pushed: - It stops if the tagged commit is not on main. - For a tag without a hyphen, the tag must match the version in Cargo.toml. A tag with a hyphen (for example v0.6.1-rc.2) becomes a pre-release and skips that check. - It runs the tests, creates the release with generated notes (or uses a release that already exists for the tag), and attaches the three builds. One workflow creates the release and builds the assets, because GitHub does not start other workflows for a release that a workflow creates with its own token. ARCHITECTURE.md describes the steps.
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
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.
The release workflow now runs when a tag that starts with
vis pushed, instead of after a release is created by hand.main.v0.6.1-rc.2, becomes a pre-release. For any other tag, the version inCargo.tomlmust match.Checked with actionlint. I also ran the tag check script locally against the real
Cargo.toml:v0.6.0passes as a full release,v0.6.1is refused, andv0.6.1-rc.2becomes a pre-release. The workflow itself first runs on the next tag push. ARCHITECTURE.md has a short "Releasing" section.