ci: upgrade GitHub Actions to Node 24 majors#6
Merged
Conversation
GitHub deprecated Node 20 action runtimes; bump every workflow action to its current Node 24 major, release notes checked at each hop: - actions/checkout v4 -> v7 (fork-PR block only hits pull_request_target/ workflow_run triggers, which no workflow here uses) - actions/setup-python v5 -> v7 (removed pip-install input unused) - actions/upload-artifact v4 -> v7, download-artifact v4 -> v8 (v5 path break affects by-ID downloads only; release.yml downloads by name; v8 digest-mismatch=error is a hardening win) - astral-sh/setup-uv v5 -> v9.0.0, pinned to the full tag since v8 dropped major tags; add activate-environment: true because since v6 python-version alone no longer activates the venv that the uv pip install / uv run steps depend on pypa/gh-action-pypi-publish@release/v1 untouched: Docker action, no Node runtime, and release/v1 is pypa's recommended ref.
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.
Summary
GitHub is deprecating Node 20 action runtimes (runners already force such actions onto Node 24 with a warning). This bumps every action in our three workflows to its current Node 24 major. Release notes were checked at each major hop; one bump required a behavioral fix.
actions/checkoutpull_request_target/workflow_runtriggers — none used hereactions/setup-pythonpip-installinput was never usedactions/upload-artifactactions/download-artifactrelease.ymldownloads by name. v8 defaultsdigest-mismatchtoerror— a hardening winastral-sh/setup-uvsetup-uv: the one real change
python-versionalone no longer auto-activates a venv.test.ymlrelied on that (theuv pip install -e/uv run pyteststeps target the exportedVIRTUAL_ENV), soactivate-environment: trueis now set explicitly, with comments updated.v9.0.0tag.prune-cachedefault tofalse— neutral for us,enable-cache: trueunchanged.pypa/gh-action-pypi-publish@release/v1is untouched: it's a Docker action (no Node runtime) andrelease/v1is pypa's recommended ref.Test plan
activate-environmentinput verified present in setup-uvv9.0.0action.yml(defaultfalse, so the explicittrueis required)testworkflow green on this PR — this is the real proof of the setup-uv venv-activation change (all 6 matrix legs, esp. the sqlite-extension assert step)release.yml/publish-mcp.ymlonly run onv*tags or manual dispatch; their bumps are validated by release-notes review above and will get live confirmation at the next release🤖 Generated with Claude Code
https://claude.ai/code/session_01Pe2ssNxcoegYYz7AsUGHPr