Skip to content

chore: bump biome $schema to match pinned CLI 2.4.11 - #544

Open
EduardF1 wants to merge 1 commit into
CoderLine:mainfrom
EduardF1:chore/biome-schema-2.4.11
Open

EduardF1 wants to merge 1 commit into
CoderLine:mainfrom
EduardF1:chore/biome-schema-2.4.11

Conversation

@EduardF1

@EduardF1 EduardF1 commented Jun 26, 2026 •

Copy link
Copy Markdown

What and why

The repo pins @biomejs/biome to ^2.4.11 (package.json, resolved to 2.4.11 in the lockfile), but biome.jsonc still declares the 2.3.0 $schema. The pinned CLI reports the drift on every run:

> npx @biomejs/biome@2.4.11 check biome.jsonc
  i The configuration schema version does not match the CLI version 2.4.11
  i   Expected:  2.4.11
      Found:     2.3.0
  i Run the command biome migrate to migrate the configuration file.

Changes

  • biome.jsonc: $schema bumped from 2.3.0 to 2.4.11, generated by biome migrate --write. One line, nothing else.

Validation

  • npx @biomejs/biome@2.4.11 lint .: same result as main (2 warnings, 1 info, no errors).
  • npx @biomejs/biome@2.4.11 check biome.jsonc: the schema-mismatch notice is gone.

Separately, npm run format on main currently rewrites 8 files (scripts/extractVsix.mts, scripts/prerelease.mts, scripts/tsnocheck.mts, src/reporter/fullJsonStreamReporter.ts, src/runtime/settings.ts, src/test/integration/yarn.test.ts, src/test/util.ts, src/workspaceWatcher.ts). That is left out of this PR on purpose; I can open it as a follow-up if you want it.

@EduardF1

Copy link
Copy Markdown
Author

Friendly ping — just flagging this biome schema chore is still open. Happy to rebase or adjust anything if it helps; no rush.

@EduardF1
EduardF1 force-pushed the chore/biome-schema-2.4.11 branch from 1889258 to f3a83b7 Compare October 1, 2026 18:47
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.

1 participant