Skip to content

chore(deps): update actions/setup-node action to v6.5.0 - #29

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/actions-setup-node-6.x
Open

chore(deps): update actions/setup-node action to v6.5.0#29
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/actions-setup-node-6.x

Conversation

@renovate

@renovate renovate Bot commented Jul 16, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change
actions/setup-node action minor v6.4.0v6.5.0

Release Notes

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

v6.5.0

Compare Source

What's Changed

Full Changelog: actions/setup-node@v6.4.0...v6.5.0


Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 was generated by Mend Renovate. View the repository job log.


Open in Devin Review

Note

Update actions/setup-node to v6.5.0 in governance-enforce workflow

Pins actions/setup-node to the commit hash corresponding to v6.5.0 in governance-enforce.yml, replacing the v6.4.0 pin.

Macroscope summarized 8e7cc17.

@changeset-bot

changeset-bot Bot commented Jul 16, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: ab3e253

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@cursor cursor 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.

Risk: low. Approved: this is a narrow Renovate bump of actions/setup-node v6.4.0→v6.5.0 in one workflow file. Cursor Bugbot was not present on this PR, so that signal was skipped; no reviewers assigned.

Open in Web View Automation 

Sent by Cursor Approval Agent: Pull Request Router and Approver

@renovate
renovate Bot force-pushed the renovate/actions-setup-node-6.x branch from 075ede5 to ab3e253 Compare July 22, 2026 04:15
@renovate
renovate Bot force-pushed the renovate/actions-setup-node-6.x branch from ab3e253 to 2f025c9 Compare August 7, 2026 00:02
@greptile-apps

greptile-apps Bot commented Aug 7, 2026

Copy link
Copy Markdown

PR author is in the excluded authors list.

@devin-ai-integration devin-ai-integration 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.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

@macroscopeapp

macroscopeapp Bot commented Aug 7, 2026

Copy link
Copy Markdown

Approvability

Verdict: Needs human review

Unable to check for correctness in 2f025c9. This is a minor version bump of actions/setup-node (v6.4.0 → v6.5.0), which is low-risk. However, the modified workflow file is owned by wave-av/streaming-team per CODEOWNERS, and the designated owners should review changes to their files.

No code changes detected at 8e7cc17. Prior analysis still applies.

You can customize Macroscope's approvability policy. Learn more.

@renovate
renovate Bot force-pushed the renovate/actions-setup-node-6.x branch from 2f025c9 to 8e7cc17 Compare August 7, 2026 00:11

@devin-ai-integration devin-ai-integration 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.

Devin Review found 1 new potential issue.

Open in Devin Review

fetch-depth: 0
persist-credentials: false
- uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
- uses: actions/setup-node@249970729cb0ef3589644e2896645e5dc5ba9c38 # v6.5.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔍 Pinned SHA cannot be verified locally; confirm it matches v6.5.0

The only change is swapping the pinned commit SHA for actions/setup-node from 48b55a0 (v6.4.0) to 249970729cb0ef3589644e2896645e5dc5ba9c38 labeled v6.5.0. SHA pinning is used consistently in this workflow (checkout is also pinned), and this is the sole setup-node reference in .github/ so no other workflow drifts out of sync. The SHA-to-tag correspondence cannot be verified from the repo alone — worth a quick check against the upstream release tag before merge.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants