Closed DilumAluthge closed 2 weeks ago
I agree with the idea of checking in the built version
@omus This is ready for another round of review.
Bump @omus @IanButterworth
I just cut a new release (v2.5.0
), and I updated the v2
alias, just so that we can test out the new release process.
We can quickly revert if something breaks.
I also updated the latest
alias.
From a quick test (https://github.com/JuliaLang/Example.jl/pull/80), everything seems to be working.
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
repo[^1].So, by having the same release process across multiple repos, this should make things easier for maintainers.
[^1]: See the devdocs here: https://github.com/julia-actions/cache/blob/main/devdocs/making_a_new_release.md
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
.