chore: pin Deno to 2.3.7 in release workflow

[kt3k]

The latest Deno (2.4.0) seems to have an issue with module resolution. Let's try to use 2.3.7 for releasing for now.

related:

• jsr publish --dry-run suddenly failing (reading tsconfig.json???) jsr-io/jsr-npm#129
• fix: pin Deno version to v2.3.7 jsr-io/jsr-npm#130

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0389303

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

[yusukebe]

@kt3k

Thanks!