Repository navigation
Actions: versions that run on Node 24 - #126
Merged
Merged
Conversation
GitHub's runners run every action on Node 24 and warn about actions built for Node 20. checkout v4 -> v7 in the four workflows; in the simulator and Teensy workflows setup-node v4 -> v7, upload-artifact v4 -> v7, upload-pages-artifact v3 -> v5, deploy-pages v4 -> v5. The inputs used are unchanged. arduino/setup-arduino-cli@v2 stays (no Node 24 release), with a comment about its warning. Simulator README: note and changelog. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VKEBDFYMW2fYcrvsHhj83s
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.
Requested by Renato · project thread
What changes
GitHub's runners now run every action on Node 24 and print a warning for an action built for Node 20 ("Node.js 20 is deprecated ... actions/checkout@v4"). The four workflows move to the versions of GitHub's own actions that are built for Node 24:
actions/checkoutactions/setup-nodeactions/upload-artifact.hex)actions/upload-pages-artifactactions/deploy-pagesThe inputs and outputs we use are the same in the old and the new version of each action (compared in their
action.yml):path,name,if-no-files-found,retention-days,node-version, anddeploy-pagesstill givespage_url. What else the new majors changed does not touch us: checkout v6 keeps the token in a separate file and v7 refuses fork code onpull_request_target(our workflows run onpull_request); setup-node v5+ caches npm packages only when apackage.jsonnames npm as the package manager (this repository has none).arduino/setup-arduino-cli@v2stays as it is: its newest release (v2.0.0) is built for Node 20 and Arduino has not published a Node 24 version. GitHub runs it on Node 24 anyway and prints the warning for that step; the step works. A comment in the Teensy workflow says so, so the warning does not look like a fault.Nothing changes in the firmware or in the pages.
Firmware/simulator/README.mdhas the note in "How it is built" and the day's changelog row.How to test
All four checks run on this pull request, because each workflow file is in its own trigger paths: Docs, Shared code, Web page simulator (build, settings arithmetic, browser check, screenshots artifact) and Teensy firmware (compile,
.hexartifact). All green = the new versions work.The Pages publication (
upload-pages-artifact@v5anddeploy-pages@v5) runs only once this is merged intomain: the "Web page simulator" run onmainmust end with the deploy job green and https://renatorgr.github.io/Boards/ still opening.Generated by Claude Code