feat: add release workflow for automated floating version tags#4
Merged
Conversation
j7an
force-pushed
the
feat/release-workflow
branch
from
342556e to
45d756b
Compare
j7an
added a commit
that referenced
this pull request
Apr 12, 2026
feat: add release workflow for automated floating version tags
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.
Summary
Adds a release workflow that manages all three semver tag levels when a release tag is pushed.
How it works
Push
v1.2.3→ workflow automatically:v1.2.3immutable (the exact patch release)v1.2floating tag (tracks latest patch:v1.2.3,v1.2.4, ...)v1floating tag (tracks latest minor+patch:v1.1.0,v1.2.3, ...)Consumer pinning options
@v1@v1.2@v1.2.3Versioning guide
v2.0.0)v1.1.0)v1.0.1)