-
Notifications
You must be signed in to change notification settings - Fork 14
chore: migrate action runtime to Node 24 #23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
+3
−3
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| 20.11.1 | ||
| 24.15.0 |
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: mattermost/action-mattermost-notify
Length of output: 89
🌐 Web query:
GitHub Actions node24 runner support requirements version 2.327.1💡 Result:
GitHub Actions runner version 2.327.1 introduces support for executing Node.js 24 actions while maintaining backward compatibility with Node.js 20. This is the minimum runner version required for Node.js 24-compatible GitHub Actions (e.g., actions/checkout v5 requires runner v2.327.1 or newer). No additional OS or hardware requirements beyond standard self-hosted runner setup are specified for Node 24 support in this version. Node 24 binaries are bundled in the runner, but Linux ARM32 lacks a Node 24 binary, falling back to Node 20 with a warning. Full enforcement of Node 24 as default occurs later (runner v2.328.0+ with feature flags), with Node 20 deprecation starting June 2, 2026.
Citations:
🌐 Web query:
GitHub Actions node24 macOS compatibility ARM32 support💡 Result:
GitHub Actions supports Node.js 24 on macOS runners, which are available in both ARM64 (standard macos-latest, macos-15) and x64/Intel (macos-15-large, macos-15-intel) architectures. Node.js 24 is pre-installed and updated regularly on these images (e.g., v24.15.0 on recent macos-15-arm64 images). The setup-node action also tests Node 24 on macOS runners. There is no ARM32 support in GitHub Actions runners for any architecture, including macOS. GitHub-hosted macOS runners do not offer ARM32 hardware. Node.js 24 does not provide official binaries for ARM32 (armv7l); official builds are for ARM64 (AArch64), x64, and others. ARM32 (32-bit ARM) support is deprecated in GitHub Actions runners, particularly for Linux ARM32, with Node 24 enforcement handling it via warnings/fallbacks to Node 20, but macOS runners are unaffected as they lack ARM32. For self-hosted runners on hypothetical ARM32 macOS hardware (uncommon, as Apple Silicon is ARM64), Node 24 would not run natively without custom builds, and GitHub Actions runner software does not support it post-Node 20 deprecation.
Citations:
🏁 Script executed:
# Check the repository structure to understand what we're working with head -50 action.ymlRepository: mattermost/action-mattermost-notify
Length of output: 1086
🏁 Script executed:
Repository: mattermost/action-mattermost-notify
Length of output: 3996
🌐 Web query:
Node.js 24 system requirements macOS minimum version compatibility💡 Result:
Node.js 24 requires macOS 13.5 (Ventura) or later for both Intel (x64) and Apple Silicon (arm64) architectures. This is the minimum supported version for pre-built binaries and running the runtime. To build Node.js from source, Xcode 16.1 or later (specifically Xcode Command Line Tools >=13 in v24.x docs, but updated to >=16.4 in main) is required, and binaries are compiled with -mmacosx-version-min=13.5 targeting macOS 13.
Citations:
Breaking change for self-hosted runners — document the new minimum runner version requirement.
Switching
runs.usingtonode24introduces a breaking change for self-hosted runner consumers. This needs to be documented explicitly inREADME.mdand considered for a major version bump when released:Parameter 'using: node24' is not supported.Currently, the
README.mddoes not document these requirements or the breaking nature of this transition. Recommend adding a "Requirements" or "Breaking Changes" section covering the minimum runner version and macOS version constraint so users on self-hosted infrastructure understand the impact before upgrading.Confirm whether this release will be published under a new major tag (e.g.
v2→v3) to prevent workflows pinned to@v2from automatically picking up the incompatible change.🤖 Prompt for AI Agents