Stream: helpdesk (published)

Topic: ✔ Specifying julia beta versions in Github Actions CI

Brenhin Keller (Apr 23 2022 at 23:06):

I'm trying to figure out the correct syntax for specifying different beta versions (e.g. 1.8.0 beta3 vs 1.8.0beta2, vs rc, etc.) in Github Actions.

For example, prior to the release of actual 1.8.0, 1.8 fails to match any version but ~1.8.0-0 runs something (presumably one of the betas). What does this version format mean and how should one use it in practice?

Brenhin Keller (Apr 23 2022 at 23:09):

@Mason Protter I think you maybe figured this out recently for StaticCompiler?

Sascha Mann (Apr 24 2022 at 06:48):

The setup-julia readme has some examples: https://github.com/julia-actions/setup-julia#examples

The -0 tells it to include all pre-releases. The tilde restricts it to patches starting with 1.8., so ~1.8.0-0 would match all versions ≥ 1.8.0 and < 1.9.0 including 1.8.0-beta2. In the range, it always picks the highest available version. You could also use ~1.8.0-beta2 which includes all pre-releases starting from beta2, e.g. beta3, rc1. Does that help?

There's also a REPL that goes through some release scenarios that you can play around with.

Notification Bot (Apr 24 2022 at 18:09):

Brenhin Keller has marked this topic as resolved.

Brenhin Keller (Apr 24 2022 at 18:09):

Awesome, thank you!

Last updated: Nov 22 2024 at 04:41 UTC