[botandbang]

uppt rewrites every workspace package.json with JSON.stringify on each release bump, which puts each files and keywords entry on its own line. Biome 1.9.4 collapses short arrays, so every release PR failed lint (the v1.1.0 PR, #85, needed a manual reformat). Biome 2 formats package.json the same way npm does, which matches uppt's output.

Changed:

• @biomejs/biome goes from 1.9.4 to 2.5.15 in all 10 workspaces, still pinned exactly.
• The root biome.json is migrated to the 2.x schema (organizeImports under assist, preset: "recommended").
• Workspace configs use Biome 2's monorepo form, "root": false with "extends": "//". static keeps its files.maxSize override.
• The files and keywords arrays in every package.json, root included, are now one entry per line.

Removed, in a second commit, what Biome 2's recommended preset flags as unused: the beforeEach, DateTime and nodevu imports in core's parseOptions.js, schedule.js and versions.js tests, the unused line loop variable in schedule.js, and the filename parameter of the four static/build/*.js scripts, which are each called with no arguments. Two warnings remain in core/test/schedule.js: the "optionsParser" tests assign data and never check it, so they assert nothing. That fix changes what the tests cover, so it goes in its own PR.

npm run lint and npm test --ws pass from a clean install. A uppt-style rewrite of each published package.json differs from the committed file only in the version line.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​biomejs/​biome@​1.9.4 ⏵ 2.5.15	+8		+1

View full report