Skip to content

feat: add major and minor standalone release tags - #127

Closed
rifisdfds wants to merge 1 commit into
masterfrom
feat/add-major-minor-standalone-tags
Closed

rifisdfds wants to merge 1 commit into
masterfrom
feat/add-major-minor-standalone-tags

Conversation

@rifisdfds

Copy link
Copy Markdown
Contributor

This PR will update any major or minor standalone tags

For example:
If 2.1.4 is released, 2 and 2.1 will get updated
If 2.2.0 is released, 2 will get updated and 2.2 will get created

This will allow us to refer to releases at major or minor version. For example, when using github actions in this shared workflow we can refer to @2 or @2.1

@rifisdfds
rifisdfds requested a review from a team as a code owner October 19, 2026 13:00

@SEQUOIIA SEQUOIIA left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable. The force push sorta sucks, but given we reuse the same tag I guess it’s a necessity

@wcarlsen

Copy link
Copy Markdown
Contributor

I cannot believe that there isn't already a Github Action that does this by default?

with:
bump_version_scheme: patch
tag_prefix: ${{ inputs.tag_prefix }}
- name: Update version aliases

@wcarlsen wcarlsen Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May I suggest that we try something like this instead https://github.com/haya14busa/action-update-semver

      - uses: haya14busa/action-update-semver@v1.5.1
        with:
          major_version_tag_only: false  # (optional, default is "false")
          tag: ${{ steps.auto-release-id.outputs.tag_name }}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI this is confirmed to work with any of these tested prefixes
"v1.2.3" "1.2.3" "dev-1.2.3" "dev-v1.2.3"

@rifisdfds

Copy link
Copy Markdown
Contributor Author

Superseded by #128

@rifisdfds rifisdfds closed this Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants