Repository navigation
fix: refresh dependencies and keep React versions aligned - #251
Merged
atomantic merged 2 commits intoNov 10, 2026
Merged
Conversation
atomantic
deleted the
cos/sys-a5765c61-dependency-updates-mwath23b/agent-285c6189
branch
November 10, 2026 15:16
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.
Summary
React was bumped to 19.3.1 while React DOM remained at 19.3.0, so every client test suite failed on import and the UI could not render. Align React DOM, group future React patch/minor updates, and include the existing client component suite in CI.
Refresh the remaining compatible patch/minor dependencies across the root and client workspaces, remove unused MSW and its dependency tree, and update the changelog and dependency backlog. No direct major upgrade is included in this PR. The preceding audit landed nine existing bot PRs and confirmed both happy-dom alerts (#88 and #92) are fixed on the default branch.
Upstream compatibility review: PM2 7.1.2 changes
filter_env: true, which this repository does not configure; sql.js 1.16.0 preserves legacy SQL behavior and is used only by test adapters. Existing Lucide icon aliases still compile. All direct registry dependencies are current; full and production npm audits report zero vulnerabilities at every severity.Test plan
npm ci --no-audit --no-fundandnpm run check:file-sizes.npm run buildfor shared, server, and client packages.npm run test:ci: 430 tests pass with coverage, including PostgreSQL integration tests against a disposable database cluster.npm test -w client -- --run: 15 tests pass; these failed before the React DOM fix.npm run test:scraper -- --workers=1 --reporter=line: 15 tests pass in Chromium.npm run start -w server: isolated loopback startup with a disposable database; health endpoint returns OK, the built UI renders in Chromium with HTTP 200 and zero page errors.npm audit --package-lock-only --jsonand the production-only audit: zero vulnerabilities; root and workspacenpm outdatedchecks return empty results.Local installs and validation ran UNCONTAINED: the required containment probe returned exit 2, stating Docker containment is disabled and nothing ran. Dependencies and generated files stayed inside isolated worktrees; no install or branch switch was performed in the live checkout.