fix: re-checkout before snapshot publish to prevent version collision

The changesets action consumes changeset files when creating the Release
PR, so the subsequent `changeset version --snapshot next` finds nothing
and publishes full release versions to the `next` tag. This causes the
actual release publish to skip those versions since they already exist
on npm.

Adding a fresh checkout + install before the snapshot step restores the
changeset files so proper snapshot versions are generated.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: wrn14897

.github/workflows/release.yaml

@@ -37,6 +37,15 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_CONFIG_PROVENANCE: true
+      # Re-checkout to restore changeset files consumed by the changesets action above.
+      # Without this, `changeset version --snapshot next` finds no changesets and
+      # publishes full release versions to the `next` tag instead of snapshots.
+      - name: Restore checkout for snapshot
+        if: steps.changesets.outputs.published != 'true' && steps.changesets.outputs.hasChangesets == 'true'
+        uses: actions/checkout@v4
+      - name: Install dependencies for snapshot
+        if: steps.changesets.outputs.published != 'true' && steps.changesets.outputs.hasChangesets == 'true'
+        run: yarn
       - name: Publish snapshot to next tag
         if: steps.changesets.outputs.published != 'true' && steps.changesets.outputs.hasChangesets == 'true'
         run: yarn run release:next