Repository navigation
ci: update major tag on release - #256
Merged
Merged
Conversation
Contributor
Coverage report
Test suite run success232 tests passing in 19 suites. Report generated by 🧪jest coverage report action from 89606dd |
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
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.
Move the corresponding major tag to the commit of each pushed stable vX.Y.Z tag, allowing consumers to use a floating major version. The workflow can also be run manually with a required stable release tag. Major-only and prerelease tags are ignored for push events; invalid manual inputs fail.
The major tag follows the selected release tag; selecting an older version later moves it backward. Tags pushed by the existing release workflow using GITHUB_TOKEN will not trigger this workflow; use the manual trigger or an appropriately authorized GitHub App token or other token that can trigger workflows.
Validation: parsed the workflow YAML, checked stable and excluded tag patterns and manual validation, verified force-updating a tag against a local Git remote, and passed lint, build, and 232 tests via hooks. The workflow has not been run on GitHub.