Simplify version-update action (trigger update for every tag, even hotfixes) - #190
Merged
Conversation
glothriel
approved these changes
Aug 24, 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.
that fancy-schmancy "hotfix" detection haven't even work..
I fixed it, but didn't push, because I realized that it's not worth over-complicating the flow - theoretically bumping on every tag shouldn't be a problem, because version bump would be triggered by:
developbranch ✔️master->developmerge, so final version in stack would point to dev again ✔️btw removal of
dev-branchisn't a breaking change - github ignores that input, so "client" repos can migrate in own pace