You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
deps: bump Node and uv to distrust compromised eMudhra CAs - #8898
Eight eMudhra intermediate CAs had trivially recoverable private keys (Mozilla bug 2083449, details). Browsers block them via OneCRL/CRLSets, but runtimes and libraries that ship their own CA bundle keep trusting them until updated.
frontend/.nvmrc, docs/.nvmrc: v24.21.0 → v24.22.2 (fix in 24.22.1). Used by the frontend PR, deploy, Chromatic, e2e and docs workflows.
api/.nvmrc: 20 → 24. Node 20 is EOL and won't get the fix.
uv 0.11.18/0.12.19 → 0.13.7 (fix in 0.13.5): mcp/DockerfileUV_VERSION, the uv-pre-commit rev, and the required-version floors in api/ and mcp/ so they stay in sync.
No Python changes needed: certifi is already at 2026.10.23 in both lockfiles, and botocore uses certifi's bundle when it's installed, so the boto3<1.36 pin can stay.
flagsmith-ee will pick this up on its next OSS merge.
How did you test this code?
uv lock --check passes for api/ and mcp/ with uv 0.13.7.
CI exercises the new Node version through frontend/.nvmrc.
The configured Node.js version changes from 20 to 24 for the API, and from v24.21.0 to v24.22.2 for documentation and frontend. The configured uv version changes from 0.11.18 to 0.13.7 in API and MCP requirements, the MCP Docker image, and the pre-commit revision.
API Docker builds using a cached older uv image can fail against the new minimum version. Pinning or refreshing that image avoids the failure; the Node pins also leave existing security-remediation gaps to address.
- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 3
Review info
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: ASSERTIVE
Plan: Advanced
Run ID: 552b940b-2237-405d-982b-b2fd004d0fb5
Commits
Reviewing files that changed from the base of the PR and between 773f1c0 and 4686a4c.
Files selected for processing: 7
.pre-commit-config.yaml
api/.nvmrc
api/pyproject.toml
docs/.nvmrc
frontend/.nvmrc
mcp/Dockerfile
mcp/pyproject.toml
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.
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
apiIssue related to the REST APIdependenciesPull requests that update a dependency filefront-endIssue related to the React Front End Dashboard
2 participants
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.
Changes
Eight eMudhra intermediate CAs had trivially recoverable private keys (Mozilla bug 2083449, details). Browsers block them via OneCRL/CRLSets, but runtimes and libraries that ship their own CA bundle keep trusting them until updated.
frontend/.nvmrc,docs/.nvmrc: v24.21.0 → v24.22.2 (fix in 24.22.1). Used by the frontend PR, deploy, Chromatic, e2e and docs workflows.api/.nvmrc: 20 → 24. Node 20 is EOL and won't get the fix.mcp/DockerfileUV_VERSION, theuv-pre-commitrev, and therequired-versionfloors inapi/andmcp/so they stay in sync.No Python changes needed:
certifiis already at 2026.10.23 in both lockfiles, and botocore uses certifi's bundle when it's installed, so theboto3<1.36pin can stay.flagsmith-ee will pick this up on its next OSS merge.
How did you test this code?
uv lock --checkpasses forapi/andmcp/with uv 0.13.7.frontend/.nvmrc.