mirror of
https://github.com/vectorize-io/hindsight.git
synced 2026-09-14 19:31:49 +08:00
Chris Bartholomew
5f3c4970da
* chore(deps): update npm dependencies in the root lockfile Raise the override floors for next, svgo, sharp, js-yaml, colord and joi, and bump the vitest devDependency across the three workspaces that declare it, so the root workspace tree resolves to current versions. Resolved versions: next 16.3.4, svgo 4.1.0, sharp 0.35.4, js-yaml 4.3.2 (3.15.2 for the two v3-scoped consumers), colord 2.10.0, joi 17.13.7, vitest and @vitest/mocker 4.1.11. Every bump stays inside the existing major line. The lockfile was regenerated with npm 11. npm 10.9.2 has an overrides-plus-workspaces bug that applies an override at the hoisted root while de-hoisting fresh copies of the old version into hindsight-all-npm and hindsight-clients/typescript, which leaves the tree worse than before. npm 11 resolves each package to a single hoisted copy. It also prunes a handful of optional peerDependency entries that npm 10 records, which accounts for most of the deletions in the lockfile diff; npm ci under npm 10.9.2 still installs from the result cleanly. * chore(deps): regenerate the agent-sdk standalone lockfile to match its manifest hindsight-tools/hindsight-agent-sdk is both a root workspace and carries its own standalone package-lock.json. The previous commit raised its vitest devDependency to ^4.1.11 but regenerated only the root lockfile, which left the standalone one recording ^4.1.2 / 4.1.5 and out of sync with its own manifest. test-hindsight-agent-sdk installs from the root lockfile, so CI would not have caught the drift, but a standalone npm ci in that directory would have failed. Regenerated with npm 11; vitest and @vitest/mocker now resolve to 4.1.11 there too.