fix: use changeset publish so releases are tagged and created

[DylanPiercey]

Description

Restore the release script to changeset publish (from npm publish).

Motivation and Context

npm publish emits no New tag: output, so changesets/action stopped creating git tags and GitHub releases from 6.0.2 onward (npm and CHANGELOG kept working). changeset publish restores both, still honoring NPM_CONFIG_TAG for non-latest dist-tags.

Checklist:

• I have updated/added documentation affected by my changes.
• I have added tests to cover my changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_015qWqoXP5JA8K3uYr1RYfRg

---

Generated by Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 23d0f62

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

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 999f1505-a113-43c9-99d2-206d06248d07

📥 Commits

Reviewing files that changed from the base of the PR and between e05ec50 and 23d0f62.

📒 Files selected for processing (1)

• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/marko-vite-releases-issue-jzivez

---

_{Comment @coderabbitai help to get the list of available commands.}