Skip to content

armgit / AiSOC

Public Imported from GitHub
0

Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.

chore(deps): consolidate three root-workspace bumps and hold the majors the name-scoped rules missed (#857)

Beenu Arora0eed4237a9f3
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
index 43ad65cec..bba80b36e 100644
--- a/.github/dependabot.yml
+++ b/.github/dependabot.yml
@@ -50,6 +50,17 @@ updates:
# (and merge it back into `dev-tooling`) once
# `eslint-plugin-react` is ESLint-10-compatible.
patterns: ["eslint*", "@typescript-eslint/*"]
+ vitest:
+ # `@vitest/coverage-v8` peer-requires `vitest` at the *exact* same
+ # version, not a range — `@vitest/[email protected]` declares
+ # `peerDependencies: { vitest: "4.1.10" }`. Ungrouped, dependabot
+ # proposes whichever one's manifest range is exceeded first and the
+ # pair drifts; `pnpm install` on this lockfile already reports
+ # `vitest 4.1.11 -> ✕ unmet peer @vitest/[email protected]: found
+ # 4.1.10`. Within a major that is survivable, which is exactly why it
+ # went unnoticed. Grouping them means the next in-major bump is one
+ # pull request that moves both or neither.
+ patterns: ["vitest", "@vitest/*"]
ignore:
# Hold `eslint` on v9: ESLint 10 removed the `context.getFilename()`
# API that `eslint-plugin-react` (bundled via `eslint-config-next`)
@@ -74,6 +85,59 @@ updates:
update-types: ["version-update:semver-major"]
- dependency-name: "@storybook/*"
update-types: ["version-update:semver-major"]
+ # `@storybook/test-runner` needs its *minor* channel held too, and the
+ # reason is a property of the rule shape rather than of this package:
+ # `update-types: ["version-update:semver-major"]` cannot hold a 0.x
+ # dependency, because for 0.x the breaking change arrives in the minor
+ # slot. It is the only pre-1.0 member of the family, so the
+ # `@storybook/*` rule above covered every other member and silently
+ # covered nothing on this one.
+ #
+ # Measured on the 0.23.0 -> 0.24.5 proposal: 0.23.0 declares
+ # `peerDependencies: { storybook: "^0.0.0-0 || ^8.2.0 || ^9.0.0" }` and
+ # 0.24.5 declares `"^0.0.0-0 || ^10.0.0 || ... || ^11.0.0-0"`. Its
+ # version line is independent of Storybook's, the way the Expo entry
+ # below describes, but its *peer* tracks the Storybook major exactly —
+ # so 0.24 is the Storybook 10 line of this package and installs against
+ # this workspace's `[email protected]` as an unsatisfied peer.
+ #
+ # Nothing in CI can catch that: no workflow runs `test-storybook`, and
+ # the only Storybook job runs `pnpm build-storybook`, which never loads
+ # the runner. The proposal was green on all 22 required checks while
+ # migrating the whole jest tree 29 -> 30 underneath it. Lift this with
+ # the rest of the family in the Storybook 10 migration.
+ - dependency-name: "@storybook/test-runner"
+ update-types: ["version-update:semver-minor"]
+ # Hold `vitest` and `@vitest/*` on v4. The group above keeps the family
+ # together inside a major; the major itself needs more than a group,
+ # because two of the three things it breaks are not dependency edges
+ # dependabot can move.
+ #
+ # Measured on the 4.1.11 -> 5.0.1 proposal, which reached CI: all 59
+ # test files and all 615 tests PASSED, and then the run failed with 59
+ # unhandled rejections reading `TypeError: Expected string coverage
+ # payload, received object` out of `V8CoverageProvider.onAfterSuiteRun`,
+ # and a coverage report of `All files | 0 | 0 | 0 | 0`. vitest 5 changed
+ # the shape of the V8 coverage payload, `@vitest/coverage-v8` stayed on
+ # 4.1.10 because its own manifest range was still satisfied, and the
+ # required `Web — Vitest smoke tests + coverage gate` is what caught it.
+ # A reader skimming "615 passed" would not have.
+ #
+ # The second break is a resolution decision this file cannot express:
+ # the root `pnpm.overrides` pins `@vitest/mocker` to `>=4.1.11 <5`,
+ # while `[email protected]` depends on `@vitest/[email protected]`. The override
+ # wins silently, so the proposal's lockfile carries a vitest 5 runtime
+ # with a vitest 4 mocker.
+ #
+ # Moving to vitest 5 therefore means one commit that bumps `vitest` and
+ # `@vitest/coverage-v8` in lockstep, raises the `@vitest/mocker`
+ # override past 5, and re-verifies the two plugins that peer-depend on
+ # vitest (`vitest-axe`, `@testing-library/jest-dom`). That is a
+ # migration, not a dependency bump.
+ - dependency-name: "vitest"
+ update-types: ["version-update:semver-major"]
+ - dependency-name: "@vitest/*"
+ update-types: ["version-update:semver-major"]
# ── apps/mobile ──────────────────────────────────────────────
#
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 68e58a685..0a4efcb7a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -23,6 +23,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
which is the reason those overrides are scoped to named parents rather than
applied workspace-wide.
+- **Three more root-workspace bumps landed as one lockfile change.**
+ `@testing-library/user-event` 14.6.4 → 14.6.7, `autoprefixer` 10.5.2 →
+ 10.6.1 and `zustand` 5.0.14 → 5.0.15, regenerated once from the three
+ manifests together: 19 insertions against 22 deletions, versus 636
+ insertions across the three individual proposals. The only transitive
+ movement is `caniuse-lite` 1.0.30001803 → 1.0.30001810, which
+ `autoprefixer` carries as a data table. Verified on the merged result
+ rather than on the three green ticks, because none of these three has a CI
+ job that exercises what it changes beyond the shared web gates:
+ `pnpm install --frozen-lockfile`, `eslint .` (0 errors), `tsc --noEmit`,
+ `vitest run --coverage` (62.17% statements, gate green), `next build` and
+ `storybook build` all pass.
+
### Fixed
- **Dependabot proposed Expo SDK 57 packages for an SDK 54 app, from an entry
@@ -52,6 +65,44 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
accepts `eslint@^10`, so the family is grouped rather than held: it can
move whenever all of it arrives in one reviewable pull request.
+- **The root entry's holds are written per dependency name, so a breaking
+ major of anything not already on the list still arrives as an ordinary
+ weekly bump.** `vitest` 4.1.11 → 5.0.1 was the demonstration. Every
+ `ignore` in that entry names a specific package someone had already been
+ burned by — `eslint`, `typescript`, `storybook`, `@storybook/*` — and
+ nothing holds majors as a class, so "stop proposing breaking majors"
+ described four names rather than a rule. Measured on the proposal: all 59
+ test files and all 615 tests passed, then the run failed with 59 unhandled
+ rejections reading `TypeError: Expected string coverage payload, received
+ object` from `V8CoverageProvider.onAfterSuiteRun`, and a coverage report of
+ `All files | 0 | 0 | 0 | 0`. vitest 5 changed the V8 coverage payload
+ shape and `@vitest/coverage-v8` stayed on 4.1.10, because its own manifest
+ range was still satisfied and it peer-requires `vitest` at an *exact*
+ version rather than a range. Separately, the root `pnpm.overrides` pins
+ `@vitest/mocker` to `>=4.1.11 <5` while `[email protected]` depends on
+ `@vitest/[email protected]`, so the override wins silently and the proposal's
+ lockfile carries a vitest 5 runtime with a vitest 4 mocker. Held at the
+ major for `vitest` and `@vitest/*`, and grouped within the major so the
+ exact-version peer pair stops drifting — `pnpm install` on the current
+ lockfile already reports `unmet peer @vitest/[email protected]: found
+ 4.1.10`, which is survivable inside a major and is why nobody had noticed.
+
+- **`update-types: ["version-update:semver-major"]` cannot hold a 0.x
+ dependency, so the Storybook hold covered every member of the family
+ except the one that needed it.** For a pre-1.0 package the breaking change
+ arrives in the minor slot, and `@storybook/test-runner` is the only
+ pre-1.0 member: 0.23.0 declares
+ `peerDependencies: { storybook: "^0.0.0-0 || ^8.2.0 || ^9.0.0" }` and
+ 0.24.5 declares `"^0.0.0-0 || ^10.0.0 || … || ^11.0.0-0"`. Its version line
+ is independent of Storybook's the way the Expo packages' are, but its peer
+ tracks the Storybook major exactly, so 0.24 is the Storybook 10 line of
+ the package and installs against this workspace's `[email protected]` as an
+ unsatisfied peer. Nothing in CI could catch it — no workflow runs
+ `test-storybook`, and the only Storybook job runs `build-storybook`, which
+ never loads the runner — so the proposal was green on all 22 required
+ checks while migrating the whole jest tree 29 → 30 underneath it. The
+ minor channel is now held for that package alongside the family's major.
+
- **The `services/api` pip entry had no holds, against two ratchet gates.**
`ruff` is declared in fourteen files (a count
`scripts/check_dependency_pins.py` enforces agreement across) and `mypy` in
diff --git a/apps/web/package.json b/apps/web/package.json
index f1614e74e..3b38bfeed 100644
--- a/apps/web/package.json
+++ b/apps/web/package.json
@@ -43,7 +43,7 @@
"recharts": "^3.9.2",
"swr": "^2.5.0",
"tailwind-merge": "^3.6.0",
- "zustand": "^5.0.14"
+ "zustand": "^5.0.15"
},
"devDependencies": {
"@storybook/addon-a11y": "^9.1.0",
@@ -54,7 +54,7 @@
"@tailwindcss/vite": "^4.3.3",
"@testing-library/jest-dom": "^7.0.1",
"@testing-library/react": "^16.3.2",
- "@testing-library/user-event": "^14.6.4",
+ "@testing-library/user-event": "^14.6.7",
"@types/cytoscape": "^3.21.0",
"@types/jest-axe": "^3.5.9",
"@types/node": "^26.1.1",
@@ -63,7 +63,7 @@
"@vitejs/plugin-react": "^6.1.1",
"@playwright/test": "^1.63.0",
"@vitest/coverage-v8": "^4.1.10",
- "autoprefixer": "^10.5.2",
+ "autoprefixer": "^10.6.1",
"axe-core": "^4.11.4",
"eslint": "^9.39.0",
"eslint-config-next": "16.3.5",
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 770e8f0f9..e1c7060be 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -154,8 +154,8 @@ importers:
specifier: ^3.6.0
version: 3.6.0
zustand:
- specifier: ^5.0.14
- version: 5.0.14(@types/[email protected])([email protected])
+ specifier: ^5.0.15
+ version: 5.0.15(@types/[email protected])([email protected])
devDependencies:
'@playwright/test':
specifier: ^1.63.0
@@ -185,8 +185,8 @@ importers:
specifier: ^16.3.2
'@testing-library/user-event':
- specifier: ^14.6.4
- version: 14.6.4(@testing-library/[email protected])
+ specifier: ^14.6.7
+ version: 14.6.7(@testing-library/[email protected])
'@types/cytoscape':
specifier: ^3.21.0
version: 3.31.0
@@ -209,8 +209,8 @@ importers:
specifier: ^4.1.10
version: 4.1.10([email protected])
autoprefixer:
- specifier: ^10.5.2
- version: 10.5.2([email protected])
+ specifier: ^10.6.1
+ version: 10.6.1([email protected])
axe-core:
specifier: ^4.11.4
version: 4.11.4
@@ -7281,8 +7281,8 @@ packages:
react-dom: 19.3.0([email protected])
dev: true
- /@testing-library/[email protected](@testing-library/[email protected]):
- resolution: {integrity: sha512-QCGwP6QrjypBLwyj5cuyfVamkaIEy/XGY+1VDehbtbQqOggYmTFpFOdWR5mPz14vX8vXLMVjDHlRNBcClyO9ew==}
+ /@testing-library/[email protected](@testing-library/[email protected]):
+ resolution: {integrity: sha512-MPCpX8bxe8zS+JmmTwLp8jd0dy1rAm60Te/SL8JrQM3qvQJcBOs1d7IefJMyZzqM3EWBrDn/LWDt1BCGu4ASfg==}
engines: {node: '>=12', npm: '>=6'}
peerDependencies:
'@testing-library/dom': '>=7.21.4'
@@ -8791,15 +8791,15 @@ packages:
resolution: {integrity: sha512-Oei9OH4tRh0YqU3GxhX79dM/mwVgvbZJaSNaRk+bshkj0S5cfHcgYakreBjrHwatXKbz+IoIdYLxrKim2MjW0Q==}
dev: true
- resolution: {integrity: sha512-rD5t5DwOjJdmSORcTq64j8MawTC+tbQ+HHqjR4NDumamy/ambn1UJrlKL+KdwujWxMkFjPM3pPHOEA9tl4767Q==}
+ resolution: {integrity: sha512-cL1Qz6ADZhcEbny/8HPfe99J6HhNoYtpX2LFLIbhgGE7Q1hlQVkYFdetDN7Id3KiQxhDrHwzlHr/YQCnZ8+xSA==}
engines: {node: ^10 || ^12 || >=14}
hasBin: true
peerDependencies:
postcss: ^8.1.0
dependencies:
browserslist: 4.29.0
- caniuse-lite: 1.0.30001803
+ caniuse-lite: 1.0.30001810
fraction.js: 5.3.4
picocolors: 1.1.1
postcss: 8.5.28
@@ -9253,9 +9253,6 @@ packages:
lodash.uniq: 4.5.0
dev: false
- resolution: {integrity: sha512-g/uHREV2ZpK9qMalCsWaxmA6ol+DX8GYhuf3T40RKoP+oL7vhRJh8LNt73PCjpnR6l14FzfPrB5Yux4PKm2meg==}
-
resolution: {integrity: sha512-TITQPUkaz+aVk5GL6NhOdwk1aEaNTSDPsGFWrTuhKGtjTF70jL/Oht2W4c6rXUe5fu7Ie19VIahAXHIIiWWNeg==}
@@ -9948,7 +9945,7 @@ packages:
peerDependencies:
postcss: ^8.4.31
dependencies:
- autoprefixer: 10.5.2([email protected])
+ autoprefixer: 10.6.1([email protected])
browserslist: 4.29.0
cssnano-preset-default: 6.1.2([email protected])
postcss: 8.5.28
@@ -16621,7 +16618,7 @@ packages:
'@csstools/postcss-text-decoration-shorthand': 4.0.3([email protected])
'@csstools/postcss-trigonometric-functions': 4.0.9([email protected])
'@csstools/postcss-unset-value': 4.0.0([email protected])
- autoprefixer: 10.5.2([email protected])
+ autoprefixer: 10.6.1([email protected])
browserslist: 4.29.0
css-blank-pseudo: 7.0.1([email protected])
css-has-pseudo: 7.0.3([email protected])
@@ -18279,7 +18276,7 @@ packages:
dependencies:
'@storybook/global': 5.0.0
'@testing-library/jest-dom': 6.9.1
- '@testing-library/user-event': 14.6.4(@testing-library/[email protected])
+ '@testing-library/user-event': 14.6.7(@testing-library/[email protected])
'@vitest/expect': 3.2.4
'@vitest/mocker': 4.1.11([email protected])
'@vitest/spy': 3.2.4
@@ -20274,8 +20271,8 @@ packages:
use-sync-external-store: 1.6.0([email protected])
dev: false
- resolution: {integrity: sha512-/8tAspM5LMPr28b3fwLYrtdj77ECpfZviaP75CMTnwO8ISyaE4GDIG/9rDDYq/cH9D2Xw2A2RXglLInmVBQB/g==}
+ resolution: {integrity: sha512-MpSEjRiBkA9crSYeOUH32rJC7SVqAbm0Fqcqge/bUi2PPoLcBWKOsG+C8mevmpr8TwXHBVkChbbJiyvkE+i/3A==}
engines: {node: '>=12.20.0'}
peerDependencies:
'@types/react': '>=18.0.0'