Skip to content

fix: migrate biome.json to Biome 2 and gate formatting in CI - #47

Merged
stephendolan merged 1 commit into
mainfrom
bb/omnifocus-cli-fix-biome-1-vs-2-config-thr_ey58w33n5t
Sep 29, 2026
Merged

stephendolan merged 1 commit into
mainfrom
bb/omnifocus-cli-fix-biome-1-vs-2-config-thr_ey58w33n5t

Conversation

@stephendolan

Copy link
Copy Markdown
Owner

bun run format:check fails on main: biome.json still uses Biome 1's files.include / ignore, which the installed Biome 2.3.11 rejects before formatting anything. CI never ran this check, so nobody noticed.

  • Config: translated with biome migrate to files.includes: ["**/src/**/*.ts", "!**/dist", "!**/node_modules"]. The **/ prefix matches how Biome 1 globs behaved (they weren't anchored to the config directory), and the ! entries take the place of ignore.
  • Reformatting: once the config loaded, the formatter flagged 3 files that had drifted while the check was broken: src/mcp/server.ts and two test files. The changes only re-wrap lines to fit lineWidth: 100. With whitespace stripped, the files are identical to main, except for the optional leading | Biome adds to a multi-line union type in errors.test.ts. No behavior changes.
  • Prevention: CI now runs bun run format:check after lint.
  • Docs: CLAUDE.md notes that the config uses the Biome 2 schema and says to run biome migrate after a major bump.

🤖 Generated with Claude Code

The installed Biome 2 rejected the Biome 1 `files.include`/`ignore`
keys, so `format:check` aborted before checking anything. Translate them
to `files.includes` with `!` negations (via `biome migrate`), apply the
formatter's pending line-wrapping to three files, and run format:check in
CI so the config and the source cannot drift unnoticed again.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@stephendolan
stephendolan merged commit 9732ba0 into main Sep 29, 2026
1 check passed
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