ci(actions): bump checkout and setup-java to v4 off the deprecated node16 runtime - #1185
Merged
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
JamieRuderman
changed the title
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.
Follow-up to #1184, which bumped
setup-nodeoff the deprecated node16 action runtime and leftcheckoutbehind.actions/checkout@v3→@v4in all three release workflows: build-electron, build-android, build-ios. (typecheck was already on v4.) No inputs changed — v4 differs in the action runtime, not the API.Second commit does
actions/setup-java@v3→@v4in build-android, the lastactions/*action on the node16 runtime. Its inputs are unchanged andjava-version: '21'is pinned explicitly, so the JDK the Android build gets stays Zulu 21 — this is a runtime bump, not a toolchain change.Every
actions/*reference in this repo is now on a supported runtime.None of these three workflows run on pull requests, so CI here validates the YAML, not the change. They will first execute on the next electron, Android or iOS release build.