ci: migrate deprecated actions to Node 24 - #17
Merged
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
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.
The workflows reference actions targeting the deprecated Node 20 runtime. Upgrade pnpm/action-setup to v5, the docs setup-node action to v5, upload-artifact to v6, and action-gh-release to v3. All changed actions declare
runs.using: node24. Existing build Node versions (24, and 22 for docs), pnpm versions, triggers, permissions, and commands remain unchanged.Validation: checked upstream action manifests and supported inputs; compared parsed workflows to confirm only action references changed;
git diff --check, frozen-lockfile UI dependency installation,make frontend, andmake pre-commitpassed.actionlint(shellcheck/pyflakes disabled) reports only the two existing invalid escaped-dot diagnostics in the release tag pattern on line 6; baseline and updated diagnostics are identical. Release and image publishing workflows were inspected without publishing artifacts.🤖 Created by Jarvis via Realmroot