chore(dev): bump biome config schema to 2.5.8 - #332
Open
fro-bot wants to merge 4 commits into
Open
Conversation
This was referenced Jul 31, 2026
fro-bot
force-pushed
the
chore/dev-biome-schema-2.5.6
branch
from
August 7, 2026 16:58
c47c335 to
3f58141
Compare
fro-bot
force-pushed
the
chore/dev-biome-schema-2.5.6
branch
from
August 8, 2026 16:36
3f58141 to
ed51b92
Compare
Matches the installed @biomejs/biome@2.5.8 (bumped on main via #359); the previous 2.5.7 target landed stale. Clears the biome lint info (schema 2.5.x vs CLI 2.5.8) reported by bun run lint on main.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates
biome.json`` from2.5.5→ `2.5.8` so it matches the installed `@biomejs/biome@2.5.8` that landed on `main` via #359.The previous target (
2.5.7, see the original commit on this branch) is now stale:mainwas bumped to@biomejs/biome@2.5.8after this PR was opened, so had #332 been merged at2.5.7the lint info (biome.jsonschema2.5.xvs CLI2.5.8) would have remained.Why a schema bump
bun run lintonmainemits one info:This PR clears that info by aligning the `` URL with the installed CLI version. No behavioral or code changes —
biome migrateproduced no other diff.Verification (on this branch, after merge from
main)bun install --frozen-lockfile— clean (280 installs across 311 packages, no peer warnings).bun run lint— clean (63 files, no infos; the schema-info is gone).bun run typecheck— clean.bun run build— clean (dist/populated).bun run test:unit— 322 pass / 0 fail / 1279 expect() calls.Branch hygiene
Branch was 10 commits behind
main; this PR now mergesmaininto the branch and stacks the2.5.7 → 2.5.8commit on top. Net diff againstmainis a single one-line schema URL change.Supersedes / Relation
2.5.7) would therefore still leave an info vs2.5.8once merged").chore/dev-biome-schema-2.5.6) was deemed cosmetic; left as-is to avoid invalidating the open PR.Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.