Repository navigation
chore(deps): refresh lockfile + migrate Biome to 2.6.4 (clears npm backlog) - #198
Merged
Merged
Conversation
Regenerates package-lock.json against the current package.json ranges, picking up the pending Dependabot bumps in one verified change instead of ~18 serially-conflicting lockfile PRs. No package.json (manifest) edits — all updates are within existing semver ranges. Covers: vitest 4.1.12, fastify 5.12.7, axios 1.21.0, hono 4.13.14, vite 8.3.5, postcss 8.5.32, find-my-way 9.10.0, undici 7.30.1, qs 6.17.1, js-yaml, brace-expansion, socket.io-parser 4.2.7, moment 2.31.0, follow-redirects 1.16.2, fast-uri 3.1.9, proxy-addr 2.0.8, source-map-js 1.2.2, handlebars 4.7.10, @grpc/grpc-js 1.14.7, joi, @faker-js/faker 10.5.0, artillery 2.0.34, @azure/msal-node 7.1.2, @azure/identity 4.14.1. A library lockfile does not affect downstream consumers; it only governs this repo's dev/CI installs. Lockfile regenerated with current npm to sidestep an arborist peer-resolution crash in the pinned global npm. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The lockfile refresh bumps @biomejs/biome 2.4.13 -> 2.6.4. Reconciles the config via `biome migrate` ($schema, rules preset) and adds an override disabling the formatter for *.md / *.yml / *.yaml so Biome 2.6.4's new Markdown/YAML formatting does not reflow the committed lattice records, workflows, and docs. `biome check` passes clean (97 files). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
gmoon
changed the title
This was referenced Oct 31, 2026
Closed
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
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
Two commits:
package-lock.jsonto latest in-range versions — picks up the pending Dependabot npm bumps in one change instead of ~18 serially-conflicting lockfile PRs. Nopackage.jsonedits; all within existing semver ranges.@biomejs/biome2.4.13→2.6.4; this runsbiome migrateand adds an override disabling the formatter for*.md/*.yml/*.yamlso Biome 2.6.4's new Markdown/YAML formatting doesn't reflow the committed lattice records, workflows, and docs.Why one PR instead of 18 merges
All the npm Dependabot PRs touch the same
package-lock.json, so they conflict serially. A library's lockfile doesn't affect downstream consumers — it only governs this repo's dev/CI installs — so refreshing it wholesale is low-consequence and clears the backlog at once.Covers / supersedes
Closes #123, #171, #172, #174, #178, #181, #182, #183, #184, #185, #186, #187, #188, #189, #190, #191, #192, #193, #194, #195, #196.
Key versions: vitest 4.1.12 · fastify 5.12.7 · axios 1.21.0 · hono 4.13.14 · vite 8.3.5 · undici 7.30.1 · qs 6.17.1 · @faker-js/faker 10.5.0 · artillery 2.0.34 · @azure/{msal-node,identity}.
(#123 was failing CI while stale; its qs 6.17.1 bump is included and validated here.)
Verification
biome check→ clean (97 files)🤖 Generated with Claude Code