chore: migrate the biome config to 2.5.4 and format the version-utils test - #240
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
Included review availability: 0 reviews are currently available. Based on recent review activity, included reviews refill at 2 per hour. Summary by CodeRabbit
WalkthroughThe pull request updates the Biome schema reference from version 2.5.3 to 2.5.4. It also reformats a named import in Merge Risk: ⚪ Minimal · up to This PR updates the Biome schema version and formats one test file without changing behavior; lint and tests are reported clean, so no actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
commit: |
a666e14 to
d881d97
Compare
@biomejs/biome moved to 2.5.4 while biome.jsonc still declared the 2.5.3 schema, so every `pnpm lint` run warns that the configuration version does not match the CLI. `pnpm biome migrate --write`; no rule or behaviour change. Signed-off-by: Kristof Siket <siket@prisma.io>
d881d97 to
d2b152f
Compare
`main` is red on `pnpm lint` since #239 (CI run 12:27Z: `failure`), and every PR that updates from main inherits it (e.g. #238).
Two errors, both fixed with biome's own tooling, no behaviour change:
`pnpm lint` is clean on this branch (817 files, 0 errors). The remaining warnings/infos on main (`noUndeclaredEnvVars`, `no-bare-cast`, one info-level `useTemplate`) are pre-existing and non-blocking; left alone.