Fix: build-release.yaml

[zygintas]

This pull request makes minor adjustments to the build and release workflow configuration. The changes focus on improving version consistency and security in the CI pipeline.

Workflow configuration updates:

• Updated the Node.js version used in the setup-node step from '22.x' to '22.14.0' for more explicit version control.
• Removed the NODE_AUTH_TOKEN environment variable from the Publish package step, which may affect npm authentication during publishing.

Summary by CodeRabbit

• Chores
  • Updated Node.js version in build pipeline to a specific stable release for improved consistency and reliability.
  • Simplified workflow configuration for the release process.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c7513ed2-3558-43d1-a64f-c97185ec5209

📥 Commits

Reviewing files that changed from the base of the PR and between 2575123 and 09f5bed.

📒 Files selected for processing (1)

• .github/workflows/build-release.yaml

---

📝 Walkthrough

Walkthrough

The GitHub Actions build-release workflow was updated with three configuration adjustments: the checkout action no longer explicitly specifies a token input, Node.js version was pinned from 22.x to 22.14.0, and the NODE_AUTH_TOKEN environment variable was removed from the npm release step.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/build-release.yaml	Updated actions/setup-node@v4 to use pinned Node.js version 22.14.0 instead of floating 22.x, removed explicit token input from actions/checkout@v4, and removed NODE_AUTH_TOKEN from the npm run release step environment variables, leaving only GITHUB_TOKEN.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Fix: build-release.yaml' is vague and generic. It merely names the file being modified without explaining what the actual fix is or what problem it addresses.	Provide a more descriptive title that explains the specific fix, such as 'Pin Node.js version and fix npm authentication in build-release workflow' or 'Remove NODE_AUTH_TOKEN from release workflow'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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 fix/build-release

📝 Coding Plan

• Generate coding plan for human review comments

---

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

Tip

CodeRabbit can generate a title for your PR based on the changes.

Add @coderabbitai placeholder anywhere in the title of your PR and CodeRabbit will replace it with a title based on the changes in the PR. You can change the placeholder by changing the reviews.auto_title_placeholder setting.