Skip to content

chore(docs): bump Blume to 1.1.3#213

Merged
SutuSebastian merged 2 commits into
mainfrom
chore/bump-blume-1.1.3
Jul 22, 2026
Merged

chore(docs): bump Blume to 1.1.3#213
SutuSebastian merged 2 commits into
mainfrom
chore/bump-blume-1.1.3

Conversation

@SutuSebastian

Copy link
Copy Markdown
Contributor

Summary

Test plan

  • docs:api
  • docs:validate --strict
  • docs:check --isolated
  • docs:build
  • docs:audit

@changeset-bot

changeset-bot Bot commented Jul 22, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: adcefba

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

coderabbitai Bot commented Jul 22, 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: 55 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: 35607fab-3fbb-4cf8-a5a5-44007de14a8c

📥 Commits

Reviewing files that changed from the base of the PR and between bada919 and adcefba.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (2)
  • apps/docs/package.json
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/bump-blume-1.1.3

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.

Blume 1.1.3 pulls ajv → fast-uri@3.1.3 (GHSA-v2hh-gcrm-f6hx, high). Pin the patched 3.1.4 release so CI audit can pass.
@SutuSebastian SutuSebastian added the docs Deploy docs site on merge to main label Jul 22, 2026
@SutuSebastian
SutuSebastian merged commit a7f1f1c into main Jul 22, 2026
13 checks passed
@SutuSebastian
SutuSebastian deleted the chore/bump-blume-1.1.3 branch July 22, 2026 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Deploy docs site on merge to main

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant