Skip to content

chore(deps): bump actions/setup-node from 4.4.0 to 6.1.0 #101

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.

Sign up for GitHub

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
dependabot wants to merge 1 commit into from
Closed

chore(deps): bump actions/setup-node from 4.4.0 to 6.1.0 #101

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ jobs:
fetch-depth: 0

- name: Setup Node ${{ matrix.node-version }}
uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v4
with:
node-version: ${{ matrix.node-version }}
cache: 'npm'
Expand Down Expand Up @@ -84,7 +84,7 @@ jobs:
uses: conventional-actions/next-version@e48c1275d221bd29e2c08f8856b91695c0a72db1 # v1

- name: Setup Node
uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v4
Copy link

@cursor cursor bot Jan 9, 2026

Choose a reason for hiding this comment

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

Removed always-auth option still used after version upgrade

Medium Severity

The always-auth: true option on line 90 is no longer supported after upgrading actions/setup-node to v6.1.0. According to the release notes, v6.1.0 explicitly "Remove always-auth configuration handling." This option was previously used to configure npm authentication for the GitHub Packages registry when publishing. The parameter will be silently ignored, potentially causing unexpected authentication behavior when publishing packages to npm.pkg.github.com.

🔬 Verification Test

Why verification test was not possible: This is a GitHub Actions configuration issue that can only be verified by running the actual workflow. The bug is confirmed by the PR description's release notes which explicitly state v6.1.0 includes "Remove always-auth configuration handling by @priyagupta108 in actions/setup-node#1436". The workflow uses always-auth: true which will no longer have any effect after this upgrade.

Fix in Cursor Fix in Web

with:
node-version: lts/*
always-auth: true
Expand All @@ -108,7 +108,7 @@ jobs:
NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

- name: Setup Node for npmjs.org
uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v4
with:
node-version: lts/*
cache: 'npm'
Expand Down