chore: use pnpm prefix for JSR commands and simplify snapshot release

[jumski]

Use pnpm to invoke JSR commands and improve release process

This PR updates our publishing scripts to use pnpm jsr instead of directly calling jsr when publishing to the JSR registry. This ensures consistent dependency resolution through pnpm.

Additionally, the snapshot release script has been improved to:

1. Use pnpm publish --recursive directly instead of going through changeset for npm publishing
2. Properly exclude the edge-worker package from npm publishing (it's JSR-only)
3. Simplify the JSR publishing command with cleaner token handling

These changes make our release process more reliable and consistent across both npm and JSR registries.

[changeset-bot]

⚠️ No Changeset found

Latest commit: afe107e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[jumski]

• chore: use pnpm prefix for JSR commands and simplify snapshot release #550 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit afe107e

Command	Status	Duration	Result
nx affected -t verify-exports --base=origin/mai...	✅ Succeeded	<1s	View ↗
nx affected -t build --configuration=production...	✅ Succeeded	<1s	View ↗
nx affected -t lint typecheck test --parallel -...	✅ Succeeded	<1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-12-12 13:57:44 UTC