[codex] Upgrade GitHub Actions to Node 24 - #20
Merged
Conversation
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.
What changed
actions/checkoutfrom v4 to v7actions/setup-pythonfrom v5 to v7Why
Both CI jobs currently emit GitHub's Node.js 20 deprecation warning. GitHub
forces those old action runtimes onto Node.js 24 for now, but the compatibility
shim is temporary. The current official v7 releases use the supported runtime.
Impact
CI keeps the same Python matrix, cache configuration, permissions, tests, and
artifact checks while removing its dependency on deprecated action runtimes.
Validation
checkout v7.0.1andsetup-python v7.0.0releasespython -m ruff check src tests streamlit_app.pypython -m pytest -q— 73 passed