[phryneas]

It's okay if a release/tag are created and staged publishing is then rejected. I can always clean up by hand. Staged publishing is worth the hassle.

[pkg-pr-new]

undefined https://pkg.pr.new/testing-library/react-render-stream-testing-library/@testing-library/react-render-stream@21

commit: 3e9388d

[Copilot]

🟢 Approval recommended

The focused wrapper and workflow changes preserve command arguments and have no identified blocking issues.

No open issues 🎉

What changed in this PR

This PR routes automated releases through npm staged publishing while allowing release and tag creation before staging approval.

Changes:

• Add an npm wrapper that redirects publish to npm stage publish and forwards other commands unchanged.
• Update the release job to Node.js >=24.18.0 <25 and add the wrapper to PATH.

File	Description
scripts/​wrap-staged/​npm	Redirects publishing to staging and removes its own PATH entry to avoid recursion.
.github/​workflows/​ci.yml	Updates the release job’s Node.js version and enables the npm wrapper.

_{Review effort: Balanced}