chore(deps): update actions/setup-node action to v6

[smartway-bot]

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-node	action	major	v3 -> v6

---

Release Notes

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

v6

Compare Source

v5

Compare Source

v4

Compare Source

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 06:59 AM, only on Monday ( * 0-6 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 Renovate Bot.

[github-actions]

🛡️ The security scan result : Repo and Config

[coderabbitai]

📝 Walkthrough

Walkthrough

GitHub Actions workflows updated to use actions/setup-node@v6 instead of actions/setup-node@v3 for Node.js provisioning. All workflow inputs and subsequent build and test steps remain unchanged.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflows .github/workflows/build-and-publish-npm-package.yml, .github/workflows/unit-tests.yml	Upgraded actions/setup-node from v3 to v6 in Node.js setup steps, maintaining all existing configuration inputs and workflow logic.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(deps): update dependency node to v24 #336: Modifies Node.js setup steps in the same workflow files, coordinating action version and Node.js version updates.

Suggested reviewers

• jonperron

Poem

🐰 From v3 to v6 we leap and bound,
Actions setup now spins around,
Workflows provisioning Node so swift,
Each pipeline gets a testing gift! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating the actions/setup-node GitHub Action from v3 to v6 across workflow files.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/actions-setup-node-6.x

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/workflows/build-and-publish-npm-package.yml (1)

15-19: ⚠️ Potential issue | 🟠 Major

Review the upgrade to actions/setup-node@v6 for breaking changes and update accordingly.

actions/setup-node@v6 has breaking changes from v3:

• Automatic npm caching is now npm-only; if the workflow uses yarn or pnpm, you must explicitly set the cache input or disable auto-caching with package-manager-cache: false
• The always-auth input has been removed (v6.1.0)

Node.js version 24 is available and stable (Active LTS, support until 2028-04-30), so no concerns there.

Verify that the workflow doesn't rely on yarn/pnpm caching auto-detection or the removed always-auth input.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/workflows/build-and-publish-npm-package.yml around lines 15 - 19,
Update the workflow usage of actions/setup-node@v6 to handle its breaking
changes: remove any use of the deprecated always-auth input and, if the project
uses yarn or pnpm (or relies on automatic package manager detection), explicitly
set the new cache behaviour using the package-manager-cache input or set
package-manager-cache: false to disable auto-caching; verify the step that
references actions/setup-node@v6 in the workflow and adjust its inputs
accordingly (e.g., remove always-auth and add package-manager-cache when
needed).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In @.github/workflows/build-and-publish-npm-package.yml:
- Around line 15-19: Update the workflow usage of actions/setup-node@v6 to
handle its breaking changes: remove any use of the deprecated always-auth input
and, if the project uses yarn or pnpm (or relies on automatic package manager
detection), explicitly set the new cache behaviour using the
package-manager-cache input or set package-manager-cache: false to disable
auto-caching; verify the step that references actions/setup-node@v6 in the
workflow and adjust its inputs accordingly (e.g., remove always-auth and add
package-manager-cache when needed).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7f513a3e-56f5-433d-9ef4-2d91ea1a9a33

📥 Commits

Reviewing files that changed from the base of the PR and between 55da96a and 480524c.

📒 Files selected for processing (2)

• .github/workflows/build-and-publish-npm-package.yml
• .github/workflows/unit-tests.yml