ci(publish.yml): npm stage publish

[chimurai]

Use npm stage publish in publish.yml

https://github.blog/changelog/2026-05-22-staged-publishing-and-new-install-time-controls-for-npm/

Summary by CodeRabbit

• Chores
  • Updated the npm publishing workflow configuration to use token-based authentication for package publishing.
  • Modified the publish command in the continuous deployment process for both beta and stable releases.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

The publish workflow is updated to explicitly pass GitHub token authentication to the npm publishing action and to replace npm publish with npm stage publish for both beta and stable release paths, preserving the existing prerelease-based conditional branching logic.

Changes

NPM Publishing Workflow Configuration

Layer / File(s)	Summary
Explicit token auth and npm stage publish command .github/workflows/publish.yml	The npm publishing step now explicitly passes ${{ secrets.GITHUB_TOKEN }} for authentication; both the beta (prerelease) and stable (release) publishing branches replace npm publish with npm stage publish while keeping the same conditional logic, access level, and tag parameters.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

A rabbit hops through workflows fine,
With tokens clear and commands divine,
From publish old to stage so new,
The auth flows straight, the path rings true! 🐰📦✨

🚥 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 summarizes the main change: updating the CI publish workflow to use npm stage publish instead of the standard npm publish command.
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 npm-stage-publish

---

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

[pkg-pr-new]

npm i https://pkg.pr.new/http-proxy-middleware@1239

commit: 5e03bec

[coveralls]

coverage: 94.67%. remained the same — npm-stage-publish into master