chore(deps): update actions/setup-node action to v7 - #201
Conversation
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe linter workflow updates its Node.js setup step from ChangesLinter workflow
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/linter.yml:
- Line 22: Update the uses entry for actions/setup-node from the mutable v7 tag
to its resolved commit SHA, while retaining the # v7 comment for readability and
automated update tooling.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 4aa03a38-ddff-4071-9ed1-61cf6d709ee2
📒 Files selected for processing (1)
.github/workflows/linter.yml
📜 Review details
⏰ Context from checks skipped due to timeout. (4)
- GitHub Check: Lint Code Base
- GitHub Check: Analyze (actions)
- GitHub Check: Analyze (javascript-typescript)
- GitHub Check: GitGuardian Security Checks
🧰 Additional context used
🪛 zizmor (1.26.1)
.github/workflows/linter.yml
[error] 22-22: unpinned action reference (unpinned-uses): action is not pinned to a hash (required by blanket policy)
(unpinned-uses)
|
|
||
| - name: Setup Node.js | ||
| uses: actions/setup-node@v6 | ||
| uses: actions/setup-node@v7 |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/usr/bin/env bash
set -euo pipefail
sha="$(gh api repos/actions/setup-node/commits/v7 --jq .sha)"
echo "Resolved actions/setup-node@v7 to $sha"
grep -n 'actions/setup-node@' .github/workflows/linter.ymlRepository: SamuelIVX/Deltabase
Length of output: 277
Pin actions/setup-node to a commit SHA.
actions/setup-node@v7 is mutable; use the resolved commit SHA instead, and keep # v7 for readability and update tooling.
Suggested change
- uses: actions/setup-node@v7
+ uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| uses: actions/setup-node@v7 | |
| uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7 |
🧰 Tools
🪛 zizmor (1.26.1)
[error] 22-22: unpinned action reference (unpinned-uses): action is not pinned to a hash (required by blanket policy)
(unpinned-uses)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.github/workflows/linter.yml at line 22, Update the uses entry for
actions/setup-node from the mutable v7 tag to its resolved commit SHA, while
retaining the # v7 comment for readability and automated update tooling.
Source: Linters/SAST tools
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
This PR contains the following updates:
v6→v7Release Notes
actions/setup-node (actions/setup-node)
v7.0.0Compare Source
What's Changed
Enhancements:
Bug fixes:
mirrorTokeningetManifestif it's provided by @deiga in #1548Documentation updates:
Dependency update:
New Contributors
Full Changelog: actions/setup-node@v6...v7.0.0
v7Compare Source
Configuration
📅 Schedule: (in timezone America/New_York)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.