Skip to content

chore(changeset): bump public docs site as patch#24

Merged
SutuSebastian merged 1 commit into
mainfrom
fix/docs-changeset-patch
Jul 19, 2026
Merged

chore(changeset): bump public docs site as patch#24
SutuSebastian merged 1 commit into
mainfrom
fix/docs-changeset-patch

Conversation

@SutuSebastian

Copy link
Copy Markdown
Contributor

Summary

  • Change public-docs-site changeset from minorpatch (docs-only).
  • Closes the stale Version PR that planned 0.3.0; Release will open a fresh 0.2.1 Version PR after merge.

Test plan

  • CI green
  • After merge: Release updates/opens Version packages at 0.2.1

Docs-only ship; keep the next release a patch (0.2.1), not minor.
@changeset-bot

changeset-bot Bot commented Jul 19, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2b1e21f

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 changesets to release 1 package
Name Type
@stainless-code/persist Patch

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

coderabbitai Bot commented Jul 19, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 5 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: 3e1f7e72-7c94-4c6d-ae9b-f043b49a705d

📥 Commits

Reviewing files that changed from the base of the PR and between 97f0bda and 2b1e21f.

📒 Files selected for processing (1)
  • .changeset/public-docs-site.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/docs-changeset-patch

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

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

@SutuSebastian
SutuSebastian merged commit aeb5048 into main Jul 19, 2026
13 checks passed
@SutuSebastian
SutuSebastian deleted the fix/docs-changeset-patch branch July 19, 2026 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant