Summary

Update to publish action to use staged publishing

Linked issue

N/A

Changes

N/A

Checklist

• Tests added or updated (or N/A with reason)
• Docs / types updated if public API changed (index.d.ts and index.d.cts)
• No breaking changes (or called out explicitly above)

Summary by cubic

Switch the release workflow to npm’s staged publishing for safer, auditable releases. Replaces npm publish with npm stage publish in CI.

Description

• Summary of changes
  • Update .github/workflows/publish.yml to run npm stage publish --provenance --access public.
• Reasoning
  • Use staged publishing to improve supply-chain security and provenance.
  • Keeps the same publish flags; only changes the publish method.
• Additional context
  • Requires npm that supports staged publishing (npm v10.8+).
  • No source or package changes.

Docs

Please update the release guide in /docs/ to:

• Note we use staged publishing (npm stage publish).
• Call out the required npm version.
• Briefly describe the staged publish flow and expectations.

Testing

• No unit tests changed; this is CI-only.
• Validate by running the publish workflow on a prerelease tag to ensure staging and release work as expected.

Semantic version impact

No impact to package semantics. Infrastructure-only change; treat as a patch (no API changes).

^{Written for commit b8d5278. Summary will update on new commits. Review in cubic}