Skip to content

chore(deps): consolidate Dependabot PRs #152–#155 (typescript-eslint + react parity) - #156

Merged
agjs merged 3 commits into
mainfrom
chore/consolidate-dependabot-2026-06-09b
Jun 9, 2026
Merged

chore(deps): consolidate Dependabot PRs #152–#155 (typescript-eslint + react parity)#156
agjs merged 3 commits into
mainfrom
chore/consolidate-dependabot-2026-06-09b

Conversation

@agjs

@agjs agjs commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Summary

Consolidates the 4 new Dependabot PRs (#152#155) into one. Two of them (#155, #153) fail CI on their own because each bumps only one side of a version pair the repo requires to move together. This PR applies all four bumps plus the companion changes that keep the cross-app invariants green.

Bumps

Why each failing PR needed companions

#155 (typescript-eslint, api) — failed typecheck + lint + test.
The shared-tool-version-parity lint-meta rule requires typescript-eslint pinned to the same version in every app that declares it. Bumping only api → ui@8.60.0, api@8.60.1 drift → fail. (#152 bumps only ui and shows green only because the parity rule runs in api's CI, which #152 doesn't trigger.) Fix: bump typescript-eslint to 8.60.1 in both apps, and the @typescript-eslint/utils override alongside it (kept equal across api+ui per package-override-parity).

#153 (react group, ui) — failed validate + Playwright.
react/react-dom 19.2.7 alone produced "mismatching versions of React and the renderer" / "Cannot read properties of null (reading 'useCallback')" in the consent-store tests. Root cause: zustand@5.0.13 declares react as an exact-pinned optional peer (→ react 19.2.6), so bumping the top-level react to 19.2.7 leaves zustand on its own nested 19.2.6 copy → two React instances. Fix: add react/react-dom 19.2.7 to overrides to collapse react to a single copy (rationale documented in //overrides), and mirror the react/react-dom/@types/react versions into apps/docs so package-override-parity's sibling-mirror check stays green.

Verification

  • apps/api bun run check ✅ (typecheck, lint, lint:meta incl. both parity rules, RULES.md, knip)
  • apps/ui bun run check ✅ + bun run test:ci ✅ (655/655 — the chore(deps)(deps): bump the react group across 1 directory with 3 updates #153 failures now pass with a single React)
  • apps/docs bun run build:ci
  • Security pre-push (gitleaks, semgrep, osv-scanner) ✅ clean on all three regenerated lockfiles
  • All three bun.lock files regenerated (frozen-install safe)

Docker-backed smoke/Playwright + Redis/Postgres integration tests run in GitHub CI (no Docker locally).

Closes

Supersedes and closes #152, #153, #154, #155.

agjs added 3 commits June 9, 2026 17:47
- openai 6.39.1 -> 6.41.0 (#154)
- typescript-eslint 8.60.0 -> 8.60.1 (#155) + @typescript-eslint/utils
  override to match

typescript-eslint must move in lockstep with apps/ui (shared-tool-version-parity
lint-meta rule), so this lands together with the UI bump.
- react / react-dom 19.2.6 -> 19.2.7, @types/react 19.2.15 -> 19.2.16 (#153)
- typescript-eslint 8.60.0 -> 8.60.1 (#152) + @typescript-eslint/utils override

Adds react / react-dom 19.2.7 to overrides. zustand declares react as an
exact-pinned optional peer (5.0.13 -> react 19.2.6), so bumping the top-level
react to 19.2.7 leaves zustand on its own nested 19.2.6 copy -> two React
instances -> 'Cannot read properties of null (reading useCallback)' /
'mismatching versions of React and the renderer' in the consent-store tests.
The override collapses react to a single copy. Rationale documented in
//overrides. This is why #153 failed validate + Playwright on its own.
- react / react-dom 19.2.6 -> 19.2.7, @types/react override 19.2.15 -> 19.2.16

Mirrors the apps/ui bumps so package-override-parity stays green: ui now
overrides react@19.2.7 and @types/react@19.2.16, and docs must resolve the
same versions (sibling-mirror check).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant