This post is about the use of julia-actions/setup-julia in GitHub Actions CI. The current major version is setup-julia@v2.
Suppose that your Project.toml file includes this compat entry for Julia:
[compat]
julia = "1.10"
And suppose that you pass min as the version input to setup-julia, eg:
- uses: julia-actions/setup-julia@v2
with:
version: 'min'
setup-julia@v2 will install Julia 1.10.0, because that’s the absolute lowest Julia version that is compatible with the Julia compat entry in your Project.toml file.
However, I (and a few other folks) find the current behavior a little surprising. I would instead like[1] min to install Julia 1.10.10 (or whatever the latest 1.10.x patch is). In other words, I’d like min to install the minimum major/minor, but the latest patch.
I think that this is probably technically a breaking change, so my plan is to make this change in setup-julia@v3.
(To be clear, if you’re currently using setup-julia@v2, your CI jobs won’t suddenly start breaking. You’ll need to upgrade to setup-julia@v3 to get the new behavior.)
What do folks think of this proposed change? Is there anyone that specifically wants the old behavior?