ci: pin GitHub Actions to Node 24 runtimes#6
Merged
Conversation
GitHub Actions removes the Node 20 runtime on 2026-09-16, and from 2026-06-16 the runner defaults to Node 24. Bump to the newest versions whose action.yml declares runs.using: node24: - actions/checkout v4 -> v6 (5 workflows) - actions/setup-python v5 -> v6 (lint, test, publish) - astral-sh/setup-uv v5 -> v7 (lint, test, publish) setup-uv stays on v7 rather than v8 to preserve this repo's pin-by-major convention: v8 stopped publishing major/minor tags, which would force full-tag pinning and forfeit automatic patch updates. No breaking change in these versions affects this repo's usage.
The publish job passed the project file to `python-version`, which expects a version spec, so setup-python fails to resolve it. Use `python-version-file`, matching the lint job. Latent until now because publish only runs on release and the pipeline has been red since 2025-07.
Same-cycle coherence for the Node 24 pin change (PR #6): a decisions.md entry capturing the v7-over-v8 setup-uv trade-off, a roadmap Done row, and a radar note to revisit setup-uv v8 / SHA-pinning under Dependabot.
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
1 participant
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.
Why
GitHub Actions removes the Node 20 runtime on 2026-09-16, and from 2026-06-16 the runner defaults to Node 24. The currently-pinned actions (
checkout@v4,setup-python@v5,setup-uv@v5) all run on Node 20.What
Bumped each action to the newest version whose
action.ymldeclaresruns.using: node24(verified live via the GitHub API):checkout@v6is applied across all 5 workflows;setup-python/setup-uvacross lint, test, and publish.setup-uv stays on v7, not v8 — v8 stopped publishing major/minor tags (
@v8no longer resolves), which would force full-tag pinning and forfeit automatic patch updates. v7 keeps this repo's pin-by-major convention while still running on Node 24. Revisit if the repo adopts SHA-pinning + Dependabot.A breaking-change scan against this repo's actual usage found no impact (checkout v6's credential-persistence change, setup-uv v6's
activate-environmentdefault flip, and v7's removedserver-urlinput none of which this repo relies on).Drive-by fix (separate commit)
publish.ymlpassed the project file topython-version(expects a version spec) instead ofpython-version-file, so the publish job would fail to resolve Python. Latent because publish only runs on release and the pipeline has been red since 2025-07.Validation
actionlintclean; no stale@v4/@v5pins remain.push.yml: lint + test matrix py3.10–3.13) runs on this push — must be green before merge.publish.ymlonly triggers on a GitHub Release, so it is not exercised by this PR. Confidence rests on its pins being identical to the validated lint/test jobs plus thepython-version-filecorrectness fix.