ci(sandbox): publish @bunny.net/sandbox in release workflow

[amir-at-bunny]

No description provided.

[bogdan-at-bunny]

@codex review

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8d25637

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 07c28f31cc

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Rewrite workspace dependencies before publishing sandbox

Publishing from packages/sandbox as-is produces a tarball whose package.json still contains "@bunny.net/openapi-client": "workspace:*". I confirmed this with npm pack and then installing the tarball in an empty project, which fails with EUNSUPPORTEDPROTOCOL Unsupported URL Type "workspace:"; npm consumers of the newly published SDK cannot install it until the internal dependency is converted to a registry version (or the package is built/packed via a step that rewrites workspace dependencies).

Useful? React with 👍 / 👎.

[jamie-at-bunny]

patch