Skip to content

fix(deps): Patch React Router and e2e advisories, add Renovate - #187

Merged
yahyafakhroji merged 4 commits into
mainfrom
fix/dependency-vulnerabilities
Nov 18, 2026
Merged

yahyafakhroji merged 4 commits into
mainfrom
fix/dependency-vulnerabilities

Conversation

@yahyafakhroji

Copy link
Copy Markdown
Contributor

Problem
The consumer UI pinned React Router 7.18.2, which falls inside the advisories published on 18 Nov. Both e2e bun lockfiles carried advisories in @modelcontextprotocol/sdk, zod, hono, qs, proxy-addr, ip-address, fast-uri and body-parser. The repo had neither a Renovate config nor a CI vulnerability scan, so nothing raised these.

Solution
The consumer UI moves to 7.18.5. Both e2e lockfiles re-resolve inside their existing ranges, which moves the MCP SDK to 1.32.2 and zod to 4.6.7. A new renovate.json extends the shared milo-os preset like the other milo-os repos. A new workflow runs the shared datum-cloud/actions vuln-scan on pull requests, pushes to main and every Monday, across npm and Go.

Tests and the build pass. Typecheck reports the same six chat-kit errors as main, which the known-errors gate already allows. osv-scanner and govulncheck report no issues.

The consumer UI pinned 7.18.2, which falls inside the React Router
advisories published on 18 Nov. 7.18.5 carries the fixes.
Re-resolved both e2e lockfiles within the existing ranges. This moves
the MCP SDK to 1.32.2 and zod to 4.6.7 and clears the hono, qs,
proxy-addr, ip-address, fast-uri and body-parser advisories.
Match the other milo-os repos by extending the shared org preset.
Call the shared datum-cloud vuln-scan workflow on pull requests, pushes
to main and a weekly schedule. Go is clean under govulncheck, so both
ecosystems are scanned.
@yahyafakhroji
yahyafakhroji requested a review from a team as a code owner November 18, 2026 22:51
@yahyafakhroji
yahyafakhroji merged commit 3f5aa3a into main Nov 18, 2026
8 checks passed
@yahyafakhroji
yahyafakhroji deleted the fix/dependency-vulnerabilities branch November 18, 2026 23:13
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.

2 participants