How to specify 1.11-rc as test target on GitHub?

General Usage
1

The title says it all…

2

When else fails, read the documentation:

Examples

  • '1.2.0' is a valid semver version. The action will try to download exactly this version. If it’s not available, the build step will fail.
  • '1.0' is a version range that will match the highest available Julia version that starts with 1.0, e.g. 1.0.5, excluding pre-releases.
  • '^1.3.0-rc1' is a caret version range that includes pre-releases of 1.3.0 starting at rc1. It matches all versions ≥ 1.3.0-rc1 and < 2.0.0.
  • '~1.3.0-rc1' is a tilde version range that includes pre-releases of 1.3.0 starting at rc1. It matches all versions ≥ 1.3.0-rc1 and < 1.4.0.
  • '^1.3.0-0' is a caret version range that includes all pre-releases of 1.3.0. It matches all versions ≥ 1.3.0- and < 2.0.0.
  • '~1.3.0-0' is a tilde version range that includes all pre-releases of 1.3.0. It matches all versions ≥ 1.3.0- and < 1.4.0.
  • 'lts' will install the latest LTS build.
  • 'pre' will install the latest prerelease build (RCs, betas, and alphas).
  • 'nightly' will install the latest nightly build.
  • '1.7-nightly' will install the latest nightly build for the upcoming 1.7 release. This version will only be available during certain phases of the Julia release cycle.
  • 'min' will install the earliest supported version of Julia compatible with the project. Especially useful in monorepos.
2 Likes
3

What is best practice:

  • test with nightly
  • test with pre
  • test with both

?

4

Yes

5

I asked if option 1,2 or 3 is best practice. “Yes” does not answer this question.

6

Indeed it does. “Yes” means take all options’