ci: bump game-ci/unity-builder v4 -> v5 (Node 24)#33
Merged
Conversation
Last remaining node20 action. v5 ships the Node.js 20 -> 24 runtime update; its breaking changes are confined to Cloud Runner/Orchestrator (unused here), so the standard hosted-runner build path (projectPath/unityVersion/targetPlatform/ buildMethod/versioning/customParameters/allowDirtyBuild) is drop-in. Re-pinned to the v5 commit SHA. Only runs on release tags, so not exercised by PR CI. Co-Authored-By: Claude Opus 4.8 (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.
Final node20 cleanup (follow-up to #29 / #32).
game-ci/unity-builderwas the last action still on the Node 20 runtime.game-ci/unity-builderv4 → v5 (SHA-pinnedd829bfc…), which ships the Node.js 20 → 24 runtime update.Breaking-change review: v5's breaking changes are confined to the Cloud Runner / Orchestrator path (S3 locking, plugin system,
Cli→PluginOptionsrename, legacy-CLI removal) — none of which this repo uses. Our build uses the standard hosted-runner inputs (projectPath,unityVersion,targetPlatform,buildMethod,versioning,version,customParameters,allowDirtyBuild), which are unchanged, so v5 is drop-in.release.ymlonly runs on release tags, so this can't be exercised by PR CI — it will be validated on the next real release. actionlint (PR-run) still checks the workflow syntax.With this merged, every GitHub Action in the repo runs on Node 24.
🤖 Generated with Claude Code