Skip to content

chore(deps): update actions/setup-node action to v7 - #201

Merged
SamuelIVX merged 1 commit into
mainfrom
renovate/major-github-actions
Jul 21, 2026
Merged

chore(deps): update actions/setup-node action to v7#201
SamuelIVX merged 1 commit into
mainfrom
renovate/major-github-actions

Conversation

@SamuelIVX

Copy link
Copy Markdown
Owner

This PR contains the following updates:

Package Type Update Change
actions/setup-node action major v6v7

Release Notes

actions/setup-node (actions/setup-node)

v7.0.0

Compare Source

What's Changed

Enhancements:
Bug fixes:
Documentation updates:
Dependency update:

New Contributors

Full Changelog: actions/setup-node@v6...v7.0.0

v7

Compare Source


Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • "every weekday"
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Updated the automated code quality workflow to use the latest Node.js setup action.

Walkthrough

The linter workflow updates its Node.js setup step from actions/setup-node@v6 to actions/setup-node@v7. Other workflow configuration remains unchanged.

Changes

Linter workflow

Layer / File(s) Summary
Update Node.js setup action
.github/workflows/linter.yml
The Setup Node.js step now references actions/setup-node@v7 instead of actions/setup-node@v6.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested labels: dependencies

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly matches the main change: upgrading actions/setup-node from v6 to v7.
Description check ✅ Passed The description directly describes the same dependency update and related release notes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/major-github-actions

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9c483f9 and 3a00aa8.

📒 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

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 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.yml

Repository: 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.

Suggested change
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

@github-actions

Copy link
Copy Markdown

Super-linter summary

Language Validation result
JSON Pass ✅
MARKDOWN Pass ✅
TYPESCRIPT_ES Pass ✅
YAML Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter

@SamuelIVX
SamuelIVX merged commit 1f27912 into main Jul 21, 2026
10 checks passed
@SamuelIVX
SamuelIVX deleted the renovate/major-github-actions branch July 21, 2026 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant