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: f0df283 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types 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 |
1 of 3 tasks
EduardF1
added a commit
to EduardF1/openapi-typescript
that referenced
this pull request
Oct 1, 2026
… hunks Keep the PR to the error propagation fix: the biome.json ignore rewrite belongs to openapi-ts#2834 and the four underscore renames in test/index.test.tsx are not needed for biome check to pass with the pinned 2.4.14.
A lint-config edit changes no published output, so it should not cut a patch release of four packages. The empty changeset keeps changeset-bot satisfied without bumping anything.
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.
Changes
The repo pins
@biomejs/biometo2.4.14(package.json), but the rootbiome.jsonand all four package configs still declare the2.3.14$schemaand use the pre-2.2.0!folder/**ignore form. The pinned CLI reports this on a clean checkout:$schemabumped to2.4.14in all five configs (whatbiome migrateemits).!**/examples/**to!**/examples,!test/**/schemas/**to!test/**/schemas,!dist/**to!dist,!test/fixtures/**to!test/fixtures,!examples/**to!examples. File-glob negations (!test/bench/**/*.min.js,!**/fixtures/**/*) are unchanged.Config only; no source or published output changes. The changeset is intentionally empty so this does not trigger a release of four packages for a lint-config edit.
How to Review
Run the command above on
mainand on this branch: the warnings and infos disappear andbiome check .still passes in every package.Checklist
docs/updated (not applicable)pnpm run update:examples(not applicable)