chore: fix publish

[aaron-steinfeld]

No description provided.

[github-actions]

Test Results

53 tests  ±0   53 ✅ ±0   13s ⏱️ -1s
15 suites ±0    0 💤 ±0 
 2 files   ±0    0 ❌ ±0 

Results for commit 654be11. ± Comparison against base commit 1537d05.

♻️ This comment has been updated with latest results.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.67%. Comparing base (1537d05) to head (654be11).
Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1296   +/-   ##
=======================================
  Coverage   99.67%   99.67%           
=======================================
  Files          49       49           
  Lines         607      607           
  Branches       35       35           
=======================================
  Hits          605      605           
  Misses          2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[aaron-steinfeld]

The docs here are wildly confusing. They state

The registry can be configured via the npm environment variable NPM_CONFIG_REGISTRY and will take precedence over the configuration in .npmrc.

which isn't what we saw. Later in the docs, it states:

Notes:

The presence of an .npmrc file will override any specified environment variables.

which is what we saw.

So trying a different approach to split the read and publish registries.

[github-actions]

🎉 This PR is included in version 7.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀