ci: bring every action up to current - #28
Merged
Merged
Conversation
checkout v4→v7, upload-artifact v4→v7, download-artifact v4→v8, setup-python v5→v7, upload-pages-artifact v3→v5, deploy-pages v4→v5, setup-uv v8.1.0→v9.0.0. checkout on v4 was emitting the Node 20 deprecation warning on every run, and the runner already force-migrates it — this collects a change that has effectively happened. setup-uv is pinned exactly because astral-sh publishes no floating major tag; `@v9` does not resolve at all, which is why the pins here have always carried a patch. Everything else uses the floating major, which is what those actions publish for. msys2/setup-msys2 stays on v2 (v2.32.0 is inside it) and gh-action-pypi-publish stays on release/v1, its maintained ref. The upload/download pair matters most: ci.yml exercises it end to end (build uploads, deploy-docs downloads), so the same pair release.yml uses is proven here rather than first at the next release. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.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
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.
actions/checkout@v4was emitting the Node 20 deprecation warning on everyrun, and the runner already force-migrates it — so this collects a change that
has effectively happened.
setup-uv is pinned exactly because astral-sh publishes no floating major
tag.
@v9does not resolve at all; that failed this PR's first CI run.It is also why every pin here has always carried a patch version. The
actions/*ones do publish floating majors, so they use them.Unchanged:
msys2/setup-msys2@v2(v2.32.0 is inside it) andpypa/gh-action-pypi-publish@release/v1, its maintained ref.The artifact pair is the part worth watching, since
release.ymluses itand a release path is not exercised by PR CI. It is covered anyway:
ci.ymluploads in
buildand downloads indeploy-docs, so the same v7→v8 pairrelease.yml depends on is proven by this PR.
Python stays at 3.12 here — it is a bash project, and Python only runs the
tooling (mdformat, bump-my-version). No interpreter matrix to widen.
🤖 Generated with Claude Code