Simplify the release process (no more build script or release branches) #281
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.
Fixes #280
After this PR, the release process of this repo becomes very simple:
vMAJOR.MINOR.PATCH
tag locally (and push it).vMAJOR
tag locally (and force-push it).This is the exact same release process that is used in the
julia-actions/cache
repo1.So, by having the same release process across multiple repos, this should make things easier for maintainers.
Benefits:
Other benefits
use
able. So, if someone wants to test out a PR before it is merged, they can simply douses: julia-actions/setup-julia@name-of-pr-branch
.Footnotes
See the devdocs here: https://github.com/julia-actions/cache/blob/main/devdocs/making_a_new_release.md ↩