Update setup-node config

[rawagner]

Summary by CodeRabbit

• Chores
  • Updated internal build and deployment configuration to improve npm package publishing reliability.

[coderabbitai]

Walkthrough

Adds two npm registry authentication configuration fields to the GitHub Actions setup-node step in the release workflow: registry-url pointing to the official npm registry and always-auth set to true for consistent authentication behavior.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Configuration \\.github/workflows/release.yaml	Added registry-url: 'https://registry.npmjs.org' and always-auth: true to the setup-node step to configure npm registry authentication during Node.js setup.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single file with straightforward configuration additions to an existing GitHub Actions step
• No runtime logic or business logic changes involved

Poem

🐰 A hop, a skip, and npm auth so fine,
Registry locked to the npm line,
Always true, always clear,
Release pipeline's here!

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Update setup-node config" directly and accurately describes the main change in the pull request. The changeset modifies the setup-node GitHub Actions step configuration by adding npm registry authentication settings (registry-url and always-auth). The title is concise, specific, and clearly communicates the primary change without vague terms or unnecessary noise. A teammate reviewing commit history would immediately understand that this PR updates the setup-node configuration.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4c95b55 and 1794d9f.

📒 Files selected for processing (1)

• .github/workflows/release.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)

• GitHub Check: tests
• GitHub Check: translation-files
• GitHub Check: format
• GitHub Check: unit-tests
• GitHub Check: circular-deps
• GitHub Check: lint

🔇 Additional comments (1)

.github/workflows/release.yaml (1)

49-54: Registry and authentication configuration is correct, but verification guidance needs update.

The always-auth parameter in setup-node@v4 writes always-auth=true to the .npmrc file, which is the correct approach. However, always-auth has been deprecated in modern npm versions and newer releases warn about the unknown config, with an open request to stop adding it by default in setup-node.

The registry and authentication settings are functionally correct for your OIDC-based publishing workflow. However, remove the npm config verification shell script from your guidance—npm config get always-auth will not show the value because always-auth is no longer a recognized npm config field in modern versions.

Instead, verify the workflow functions correctly by running a test release and confirming the npm publish step completes without authentication errors. If you see npm warnings about unknown config always-auth, consider removing the always-auth: true input to silence them while maintaining registry-url configuration.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ammont82, rawagner

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [ammont82,rawagner]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rawagner]

/cherry-pick releases/v0.1-chatbot

[openshift-cherrypick-robot]

@rawagner: new pull request created: #3233

Details

In response to this:

/cherry-pick releases/v0.1-chatbot

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.