build(deps): sync biome.json schema with installed biome version - #300
Conversation
npm dedupe --dry-run reports zero drift against origin/dev/v1.7 as of 4ddbc85 — the lockfile is already clean (chore(deps): lock file maintenance #275 already deduped it). The only real issue found was biome.json's $schema pinned to 2.4.13 while package-lock.json already has @biomejs/biome at 2.5.8, which biome itself flags as a schema version mismatch. Bumped the $schema URL to match.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 54 minutes Limit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
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. Comment |
biggest-littlest
left a comment
There was a problem hiding this comment.
Approved. One-line schema sync, verified it drops a config notice and changes nothing else.
Found while cleaning up after the #298 promotion: an unpushed commit sitting in
.claude/worktrees/lockfile-dedupefrom an earlier session. Verified it is still valid and cherry-picked it rather than losing it.biome.jsondeclaredhttps://biomejs.dev/schemas/2.4.13/schema.jsonwhile the installed CLI is 2.5.8, so editors were validating the config against a schema two minors behind.One line. It also drops one of the two config notices
biome checkemits:The surviving notice is real and separate —
recommendedis deprecated in favour ofpresetas of Biome 2.5 — and is not touched here. The two warnings are pre-existingnoImgElementfindings inwebsite/src/components/star-history.tsx.Related but deliberately not bundled: #297, where
files.includeshas no**/*.mjsand 38 tracked files go unlinted. That one is a 38-file diff and deserves its own PR.