add new tag release workflow for major tags #222
Merged
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.
This pull request adds a new workflow for updating major release tags. These changes are inspired by the way folks are doing things over at
actions/checkout
.This pull request also adds a rough maintainer guide document that helps to describe the release process
How and why?
In the
actions/checkout
repo, you can point to a version such asactions/checkout@v4
and it will actually use the latestv4
tag. For example, ifv4.1.1
exists (and it does), by selecting the major release tag ofv4
it will be used because thev4
release tag gets updated to point to the latestv4.x.x
release.This pull request adds a new workflow that can triggered manually by the maintainers of this project to ensure that the latest release tag is up-to-date with the "major release tag".