Repository navigation
CI: move every GitHub Action to a Node 24 release - #8599
Merged
Merged
Conversation
Node 20 actions are deprecated on GitHub's runners, and IsaacShelton/update-existing-release still runs on Node 16 (no newer release), so: - actions/checkout v4 -> v6 (as of.yml already uses) - actions/upload-artifact v4 -> v6 - hendrikmuhs/ccache-action v1.2.14 / v1.2.17 / v1.2.23 -> v1.2.24 - awalsh128/cache-apt-pkgs-action v1.6.0 -> v1.6.3 (v1.6.0 calls actions/cache and upload-artifact on Node 20; @latest is already 1.6.3) - softprops/action-gh-release v2.1.0 -> v3 (commented out in nightly.yml) - manual-release.yml: update-existing-release replaced by the gh CLI, as nightly.yml already does: create the release if it's missing, set its title, upload the packages with --clobber (replace: true)
…release, as apothecary The fix in softprops/action-gh-release#852 (asset-only uploads to an existing release no longer fail with HTTP 403), at the commit openframeworks/apothecary's bleeding workflows already pin; v3, node24.
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.
GitHub's runners have deprecated actions on Node 20, and
IsaacShelton/update-existing-releaseis still on Node 16 (its latest release, v1.3.5, too). This moves every action in.github/workflowsto a release whoseaction.ymldeclaresusing: node24:actions/checkoutof.ymlalready usesactions/upload-artifacthendrikmuhs/ccache-actionawalsh128/cache-apt-pkgs-actionactions/cache/upload-artifacton node20)@latestalready resolves to it)softprops/action-gh-releasenightly.yml)danoli3/action-gh-release@ec40b04(v3 + softprops/action-gh-release#852, the 403 fix for asset-only uploads; the commitopenframeworks/apothecary'sbleedingworkflows already pin)IsaacShelton/update-existing-releaseghCLImanual-release.yml's "Update Release" step now uses theghCLI, likenightly.ymlalready does: it creates the release if it's missing, sets its title (not a prerelease), and uploads the packages with--clobber(the oldreplace: true). The inputs go throughenv, not inline in the script.Unchanged, already node24:
actions/setup-java@v5,microsoft/setup-msbuild@v3,msys2/setup-msys2@v2.checkoutv6 andupload-artifactv6 only change the runtime for these uses (v7 of each also exists; its changes are ESM internals and new optional inputs).