Skip to content

build(deps): sync biome.json schema with installed biome version - #300

Merged
scttbnsn merged 1 commit into
dev/v1.7from
build/biome-schema-sync
Aug 20, 2026
Merged

build(deps): sync biome.json schema with installed biome version#300
scttbnsn merged 1 commit into
dev/v1.7from
build/biome-schema-sync

Conversation

@scttbnsn

Copy link
Copy Markdown
Contributor

Found while cleaning up after the #298 promotion: an unpushed commit sitting in .claude/worktrees/lockfile-dedupe from an earlier session. Verified it is still valid and cherry-picked it rather than losing it.

biome.json declared https://biomejs.dev/schemas/2.4.13/schema.json while 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 check emits:

before: Checked 117 files. Found 2 warnings. Found 2 infos.
after:  Checked 117 files. Found 2 warnings. Found 1 info.

The surviving notice is real and separate — recommended is deprecated in favour of preset as of Biome 2.5 — and is not touched here. The two warnings are pre-existing noImgElement findings in website/src/components/star-history.tsx.

Related but deliberately not bundled: #297, where files.includes has no **/*.mjs and 38 tracked files go unlinted. That one is a 38-file diff and deserves its own PR.

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.
@vercel

vercel Bot commented Aug 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sockguard-website Ready Ready Preview Aug 20, 2026 3:02am

@coderabbitai

coderabbitai Bot commented Aug 20, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

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 @coderabbitai review or push new commits to the PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 70a64931-0467-4317-9d37-7ab826a944a7

📥 Commits

Reviewing files that changed from the base of the PR and between 8ed7feb and 7decdc0.

⛔ Files ignored due to path filters (1)
  • CHANGELOG.md is excluded by !CHANGELOG.md
📒 Files selected for processing (1)
  • biome.json

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.

@biggest-littlest biggest-littlest left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. One-line schema sync, verified it drops a config notice and changes nothing else.

@ALARGECOMPANY ALARGECOMPANY left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved.

@scttbnsn
scttbnsn merged commit 650a5ec into dev/v1.7 Aug 20, 2026
57 of 58 checks passed
@scttbnsn
scttbnsn deleted the build/biome-schema-sync branch August 20, 2026 11:08
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.

3 participants