tests.yml: only enforce the pre lane for release candidates#108
Merged
ChrisRackauckas merged 1 commit intoJul 5, 2026
Merged
Conversation
The `pre` channel installs the latest Julia prerelease. Early alphas/betas -- and the case where `pre` just resolves to the current stable release (no newer prerelease exists) -- aren't worth blocking CI on; only a release candidate is close enough to a release to matter. Add a `prerelease-gate` step (runs only on the `pre` lane) that reads the resolved Julia version after setup-julia: if its first prerelease identifier starts with `rc`, build+test run normally; otherwise they are skipped and the lane reports success. Gated steps: develop-sources, apt install, buildpkg, the group-env write, and julia-runtest. Every other julia-version runs unchanged (the gate step is skipped for them, and `outputs.run` is empty, which the `!= 'false'` guard treats as "run"). Complements the existing `continue-on-error` on `nightly`: `pre` on an RC still fails loudly (real signal), but a beta/alpha/stable `pre` no longer produces noise CI failures. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
Makes the centralized
tests.ymlprelane pass unless the prerelease is a release candidate.The
prechannel installs the latest Julia prerelease. Early alphas/betas — and the case whereprejust resolves to the current stable release (no newer prerelease exists, sopre == 1) — aren't worth blocking CI on. Only a release candidate is close enough to a real release to be worth enforcing.How
A new
prerelease-gatestep runs only on theprelane, aftersetup-julia. It reads the resolved Julia version:rc(e.g.1.13.0-rc1) → build+test run normally (can fail — real signal),beta/alpha/DEV, or no prerelease at all) → build+test are skipped and the lane reports success, with a::notice::explaining why.Gated steps: the
[sources]develop helper, apt install,julia-buildpkg, the group-env write, andjulia-runtest. Every otherjulia-versionis unaffected — the gate step is skipped for them, leavingoutputs.runempty, which the!= 'false'guard treats as "run".Validated: RC → run; beta/alpha/stable/DEV → skip; non-pre → run (truth-tabled locally against real
VersionNumbers). YAML parses.Fleet-wide behavior change to the
prelane → a minor bump on release. Draft — ignore until reviewed by @ChrisRackauckas.