ci: fix npm publish

[moabu]

Prepare

• Read PR guidelines
• Read license information

---

Description

Target issue

closes #issue-number-here

Implementation Details

---

Test and Document the changes

• Static code analysis has been run locally and issues have been fixed
• Relevant unit and integration tests have been added/updated
• Relevant documentation has been updated if any (i.e. user guides, installation and configuration guides, technical design docs etc)

Please check the below before submitting your PR. The PR will not be merged if there are no commits that start with docs: to indicate documentation changes or if the below checklist is not selected.

• I confirm that there is no impact on the docs due to the code changes in this PR.

Summary by CodeRabbit

• Chores
  • Updated build automation to use environment-based authentication for package publishing, streamlining the release process.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

Modified the cedarling WASM CI/CD workflow to use NODE_AUTH_TOKEN environment variable for npm authentication during publishing, replacing the explicit npm login command.

Changes

Cohort / File(s)	Summary
npm Authentication Enhancement .github/workflows/build-packages.yml	Added NODE_AUTH_TOKEN environment variable sourced from secrets.NPM_TOKEN to the Build WASM step; removed explicit npm login command in favor of token-based authentication.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• ci: update build package #13221: Modifies the same cedarling WASM CI workflow to adjust authentication and publishing mechanism.

Suggested labels

area-CI, comp-jans-cedarling

Suggested reviewers

• 0xtinkle
• ossdhaval

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is largely incomplete: Target issue placeholder is unfilled, Implementation Details section is empty, and required checklists are mostly unchecked.	Fill in the target issue reference, provide implementation details explaining the NODE_AUTH_TOKEN change, and complete the remaining checklist items or document why they are not applicable.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'ci: fix npm publish' clearly and specifically summarizes the main change—fixing npm publish in CI configuration.
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
• Post copyable unit tests in a comment
• Commit unit tests in branch ci-fix-cedarling-npm

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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

[mo-auto]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.