Repository navigation
Tag releases v<version> and stop marking them pre-release - #12
Merged
Merged
Conversation
jon-cook-sigma
approved these changes
Oct 26, 2026
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.
Summary
Starting with 1.0.0, releases are no longer beta. The
Releaseworkflow now tagsv<version>(for examplev1.0.0) instead ofv<version>-beta, names archives with the same slug (v1-0-0), and publishes a regular release instead of a pre-release.Existing
v0.x.y-betareleases are unchanged.Testing
Only the tag name, the archive slug and the
--prereleaseflag change. The version check, the "already released" check and the archive steps are untouched. The next merged version bump will exercise this.