feat: automatically publish floating tags - #5
Merged
Conversation
![ai-developer[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
When a new release (e.g. v1.2.3) is published, this workflow uses actions/publish-action to update the floating major and minor version tags (e.g. v1, v1.2) so users referencing `@v1` always get the latest. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
janbuchar
changed the title
janbuchar
approved these changes
May 20, 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
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
.github/workflows/release.ymlthat triggers on every published releaseactions/publish-action@v0.3.0to automatically move the floating major version tag (e.g.v1) to point at the newly released commit whenever a version likev1.2.3is publishedWhy
Users referencing
uses: apify/setup-apify-cli-action@v1in their workflows expect to always get the latestv1.x.xrelease. Without this workflow thev1tag was never updated, so it stayed stuck at the firstv1release. This is the same pattern as referenced in apify/crawlee-python#1880.Test plan
v1.0.1) and confirm thev1tag is moved to that commit@v1picks up the new version🤖 Generated with Claude Code