ci: bump actions off deprecated Node 20 + add job timeouts - #5
Merged
Conversation
GitHub is force-running our actions on Node 24 because they target the now- deprecated Node 20. Bump to current majors: - actions/checkout v4 -> v7 - actions/setup-python v5 -> v6 - actions/upload-artifact v4 -> v7 - actions/download-artifact v4 -> v8 - astral-sh/setup-uv v4 -> v8 Also add timeout-minutes to every job (tests/coverage/release) and to the hang-prone external steps (tox, build, PyPI publish), so a stuck runner can't burn the 6-hour default.
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
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
GitHub runners are force-running our workflow actions on Node 24 because the pinned versions still target the now-deprecated Node 20. This bumps them to current majors and removes the deprecation warnings.
Also
Added
timeout-minutesto every job (tests20,coverage10,release15) and to the hang-prone external steps (tox run,uv build, PyPI publish), so a stuck runner can't run up against GitHub's 6-hour default.No functional/runtime change to the package — CI plumbing only.
🤖 Generated with Claude Code