chore: keep major version in line with released version#14
Merged
Conversation
barakmich
previously approved these changes
Feb 18, 2026
barakmich
left a comment
There was a problem hiding this comment.
Seems fine, so long as you're okay with getting the Github spam
be961a3 to
f64ed9c
Compare
barakmich
approved these changes
Feb 18, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Most github actions are built to let you just specify the major version and let the rest of it float. I thought this was something built into how github actions works, but it turns out they just want you to keep the major tag updated in line with the normal semver.
This adds an action which will do that automatically when we update the version of this action.
Changes
Testing
Review.