Tracking issue for the loose ends after the CI-centralization campaign (centralized reusable workflows + tag-based releases now in place).
1. Branch-protection required-status-check names
Migrating a repo to the reusable workflows changes its job/check names (e.g. test (...) → Tests / Tests - <group>, format-check / runic → Runic Format Check, etc.). Any repo whose branch protection lists specific required checks needs those entries updated, or PRs there get stuck "waiting" on checks that no longer report under the old name. This is per-repo admin (Settings → Branches). No automation; flagging so it's done as repos are noticed.
2. Decide the fate of the JuliaFormatter format-check.yml
The ecosystem standardized on Runic (runic.yml@v1, ~134 repos). The old JuliaFormatter-based format-check.yml@v1 now has effectively one consumer left (JumpProcesses.jl). Either migrate JumpProcesses to runic.yml and retire format-check.yml, or keep it documented as the opt-in JuliaFormatter path. (Runic adoption requires the repo's code to be Runic-formatted, so a one-time runic --inplace commit comes with the switch.)
3. Triage first runs of the newly-broadened CI
Two recent defaults will surface real issues on first runs across the fleet — by design, but worth watching:
num-threads defaults to auto (hosted = vCPUs, self-hosted guarded to 2): repos with latent thread-safety bugs or tests assuming nthreads()==1 may newly fail → fix the race or set num-threads: "1".- Sublibrary downgrade tests all
lib/* with no exclusions: floor failures should be fixed via [compat] lower-bound bumps (see Optimization.jl#1215, BoundaryValueDiffEq.jl#498), not re-exclusion.
Also: big Runic adoptions deferred
Catalyst and JumpProcesses lacked Runic; their whole-repo first-format is large and was intentionally kept out of the CI-migration PRs (#1478 / #597). A separate Runic-formatting PR for each is the clean way to adopt it.
Generated from the CI-centralization work; ignore-until-reviewed by @ChrisRackauckas.
Tracking issue for the loose ends after the CI-centralization campaign (centralized reusable workflows + tag-based releases now in place).
1. Branch-protection required-status-check names
Migrating a repo to the reusable workflows changes its job/check names (e.g.
test (...)→Tests / Tests - <group>,format-check / runic→Runic Format Check, etc.). Any repo whose branch protection lists specific required checks needs those entries updated, or PRs there get stuck "waiting" on checks that no longer report under the old name. This is per-repo admin (Settings → Branches). No automation; flagging so it's done as repos are noticed.2. Decide the fate of the JuliaFormatter
format-check.ymlThe ecosystem standardized on Runic (
runic.yml@v1, ~134 repos). The old JuliaFormatter-basedformat-check.yml@v1now has effectively one consumer left (JumpProcesses.jl). Either migrate JumpProcesses torunic.ymland retireformat-check.yml, or keep it documented as the opt-in JuliaFormatter path. (Runic adoption requires the repo's code to be Runic-formatted, so a one-timerunic --inplacecommit comes with the switch.)3. Triage first runs of the newly-broadened CI
Two recent defaults will surface real issues on first runs across the fleet — by design, but worth watching:
num-threadsdefaults toauto(hosted = vCPUs, self-hosted guarded to 2): repos with latent thread-safety bugs or tests assumingnthreads()==1may newly fail → fix the race or setnum-threads: "1".lib/*with no exclusions: floor failures should be fixed via[compat]lower-bound bumps (see Optimization.jl#1215, BoundaryValueDiffEq.jl#498), not re-exclusion.Also: big Runic adoptions deferred
Catalyst and JumpProcesses lacked Runic; their whole-repo first-format is large and was intentionally kept out of the CI-migration PRs (#1478 / #597). A separate Runic-formatting PR for each is the clean way to adopt it.
Generated from the CI-centralization work; ignore-until-reviewed by @ChrisRackauckas.