Add floating major version tag workflow#45
Open
dc-larsen wants to merge 1 commit intoSocketDev:mainfrom
Open
Conversation
Adds a GitHub Actions workflow that automatically updates a floating major version tag (e.g., v1) whenever a new release is published. This lets consumers reference SocketDev/socket-basics@v1 to always get the latest release without pinning to a specific version.
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
2 participants
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
v1)SocketDev/socket-basics@v1instead of pinning to a specific version like@1.1.3actions/checkout(@v4),actions/setup-node(@v4), etc.How it works
When a release is published (e.g.,
1.1.4), the workflow:v1)v1tag if presentv1pointing to the release commitTest plan
v1tag is created/updatedSocketDev/socket-basics@v1resolves to the latest release