fix(release): include root package in Bun workspaces for changesets

[SutuSebastian]

Summary

• Release failed after feat(docs): ship public docs site at stainless-code.com/persist #20: Found changeset public-docs-site for package @stainless-code/persist which is not in the workspace.
• Bun workspaces: ["apps/*"] meant manypkg/changesets only saw apps/docs. Include "." so the publishable root is a workspace member; ignore @stainless-code/persist-docs.

Test plan

• Local bun run version gets past workspace discovery (needs GITHUB_TOKEN for changelog)
• CI green
• After merge: Release opens "Version packages" PR for public-docs-site

[changeset-bot]

⚠️ No Changeset found

Latest commit: e915f1d

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

@SutuSebastian, you've reached your PR review limit, so we couldn't start this review.

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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4c64cfdf-1809-4f64-9a31-7f52a9f15889

📥 Commits

Reviewing files that changed from the base of the PR and between cb6ca1d and e915f1d.

📒 Files selected for processing (3)

• .agents/lessons.md
• .changeset/config.json
• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/changeset-root-workspace

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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