chore: align Biome config with pinned 2.4.14 and modern folder-ignore syntax#2834
Open
EduardF1 wants to merge 2 commits into
Open
chore: align Biome config with pinned 2.4.14 and modern folder-ignore syntax#2834EduardF1 wants to merge 2 commits into
EduardF1 wants to merge 2 commits into
Conversation
… syntax The repo pins @biomejs/biome to 2.4.14, but every biome.json still declares the 2.3.14 \\\ and uses the pre-2.2.0 \!folder/**\ ignore syntax. Under the pinned CLI this surfaces 5 schema-version mismatch notices and 5 lint/suspicious/useBiomeIgnoreFolder warnings on a clean checkout. - bump \\\ to 2.4.14 in the root and all four package configs (what \�iome migrate\ emits) - adopt the new folder-ignore syntax (\!dist/**\ -> \!dist\, etc.) via Biome's own safe fix; file-glob negations are left untouched \�iome check\ on the config files is now clean. No source or ignore-semantics change -- folder ignores keep the same meaning per Biome's safe fix. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
👷 Deploy request for openapi-ts pending review.Visit the deploys page to approve it
|
🦋 Changeset detectedLatest commit: 130cd3d The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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
1 participant
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.
What and why
The repo pins
@biomejs/biometo 2.4.14 (seepackage.json), but everybiome.jsonstill declares the 2.3.14$schemaand uses the pre-2.2.0!folder/**ignore syntax. Running the pinned CLI on a clean checkout surfaces config drift:The configuration schema version does not match the CLI version 2.4.14->Run the command biome migrate)lint/suspicious/useBiomeIgnoreFolderwarnings (Since version 2.2.0, ignoring folders doesn't require the trailing /**)This is the same lint surface contributor PRs hit (e.g. the
biome checkstep in CI), so cleaning it up keeps the signal clean.Changes
$schemato2.4.14in the root config and all four package configs — exactly whatbiome migrateemits.openapi-fetch:!**/examples/**->!**/examples,!test/**/schemas/**->!test/**/schemasopenapi-react-query:!dist/**->!dist,!test/fixtures/**->!test/fixturesopenapi-typescript:!examples/**->!examples!test/bench/**/*.min.js,!**/fixtures/**/*) are intentionally left unchanged.Config-only; no source or ignore-semantics change (folder ignores keep the same meaning per Biome's safe fix).
Validation
The fixes were generated with
biome check --write+biome migrate(schema bump), not hand-edited.