Skip to content

fix(biome): align the config schema with the version actually installed - #917

Open
tobyhede wants to merge 1 commit into
mainfrom
fix/biome-config-schema
Open

fix(biome): align the config schema with the version actually installed#917
tobyhede wants to merge 1 commit into
mainfrom
fix/biome-config-schema

Conversation

@tobyhede

Copy link
Copy Markdown
Contributor

One line. code:check currently exits 1 on main for a reason unrelated to any code in the tree.

biome.json:2:14 deserialize
  i The configuration schema version does not match the CLI version 2.5.3
  > 2 │   "$schema": "https://biomejs.dev/schemas/2.5.2/schema.json",

package.json has required ^2.5.3 and pnpm-lock.yaml has resolved 2.5.3 since before this was noticed; only biome.json was left behind at 2.5.2.

Why it has stayed hidden: a node_modules that still holds 2.5.2 passes. It fails the moment the tree is brought in line with its own lockfile — which is what pnpm install --frozen-lockfile does on every CI run. Found while running a plain pnpm install on a branch off main.

Extracted from #915 so it does not wait on a large review.

`biome.json` declared schema 2.5.2 while `package.json` has required
`^2.5.3` and the lockfile has resolved 2.5.3 since before this branch —
so `biome check` exits 1 with "The configuration schema version does not
match the CLI version 2.5.3", and `code:check` fails for a reason unrelated
to any code in the tree.

It stayed hidden because node_modules on this machine still held 2.5.2; a
`pnpm install` that brings the tree in line with its own lockfile is what
surfaces it, which is exactly what CI does on every run.
@tobyhede
tobyhede requested a review from a team as a code owner August 19, 2026 02:46
@changeset-bot

changeset-bot Bot commented Aug 19, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 8d47bd2

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

@coderdan coderdan left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Took me a while, this one. Please refrain from submitting enormous PRs :p

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.

2 participants