chore: align biome.json schema with the installed CLI - #38
Merged
Conversation
Closes #37. The pinned 2.4.11 schema against the newer installed CLI (2.4.15) produced an info-level diagnostic on every lint run.
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.
Closes #37.
The
biome.json$schemapinned2.4.11, but the installed Biome CLI is2.4.15, so everypnpm lintrun emitted a schema-version-mismatch info diagnostic. This bumps the$schemaversion segment to match the installed CLI. Nothing else changes.Evidence
Before (
$schema= 2.4.11):After (
$schema= 2.4.15):Zero info diagnostics, exit 0.
Also verified:
pnpm lint:fixmodifies nothing,pnpm testpasses (443/443),pnpm typecheck:testpasses.