forked from react-native-webview/react-native-webview
-
Notifications
You must be signed in to change notification settings - Fork 6
chore: pin external GitHub Actions to commit SHAs #41
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
joel-phantom
wants to merge
1
commit into
master
from
autopilot/sec-7928-patch-remaining-repos-with-unpinned-github-actions-from-sec
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
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
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
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
Oops, something went wrong.
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
🌐 Web query:
Is actions/setup-node v3 still actively maintained, and are there any official recommendations to migrate workflows from v3 to v4?💡 Result:
No, actions/setup-node v3 is not actively maintained. The last release for v3 was v3.0.0 in February 2022. Active development and releases are on v6 (latest v6.3.0 in March 2026), with v4, v5, and v6 receiving updates including dependency bumps and feature enhancements into 2026. Official documentation and examples use v6, and GitHub Docs recommend v4 or later. Yes, there are official recommendations to migrate from v3 to v4 (and newer). The repository README lists breaking changes for v4, v5, v6, implying migration from older versions like v3. Issues and deprecation notices for older versions (e.g., v2 relying on deprecated cache) urge upgrading to v4. GitHub Docs examples use actions/setup-node@v4. Stack Overflow and issues highlight Node 16 deprecation in v3 actions, recommending v4 which uses Node 20+.
Citations:
🏁 Script executed:
Repository: phantom/react-native-webview
Length of output: 851
Upgrade
actions/setup-nodefrom v3 to v4 for consistency and maintenance.The release workflow uses
setup-node@v3, which has been unmaintained since February 2022. All other CI workflows (android-ci, detox, ios-ci, macos-ci, windows-ci) usev4, which receives ongoing updates and supports Node.js 20+. Aligning to v4 removes the maintenance drift and aligns with GitHub's official recommendations for migration.🤖 Prompt for AI Agents