Skip to content

fix(deps): bump simple-git in nuxt-api to patch GHSA-hffm-xvc3-vprc#307

Merged
WhatIfWeDigDeeper merged 3 commits into
mainfrom
fix/bump-simple-git-rce
May 6, 2026
Merged

fix(deps): bump simple-git in nuxt-api to patch GHSA-hffm-xvc3-vprc#307
WhatIfWeDigDeeper merged 3 commits into
mainfrom
fix/bump-simple-git-rce

Conversation

@WhatIfWeDigDeeper
Copy link
Copy Markdown
Owner

@WhatIfWeDigDeeper WhatIfWeDigDeeper commented May 6, 2026

Summary

Resolves the high-severity Remote Code Execution advisory GHSA-hffm-xvc3-vprc by bumping the transitive simple-git from 3.35.2 → 3.36.0 (via npm audit fix). Pulled in via nuxt → @nuxt/devtools → simple-git. Other packages in the monorepo do not depend on simple-git, so no other lockfiles change.

Note on wording: "patch" in the PR title is used as a verb ("apply a fix") — it does not imply a semver patch-level bump. 3.35.2 → 3.36.0 is a minor bump, which is what npm audit fix recommends as the smallest available fix for this advisory.

CI's audit:ci:all step has been failing on this advisory on every PR opened against main, blocking merges.

This commit was cherry-picked from feat/understand-codebase-graphs (commit f063bf3) so the fix can land independently of that feature branch's review cycle.

Test plan

  • cd nuxt-api && npx -y audit-ci --config .auditconfig.json passes locally.
  • CI audit:ci:all passes on this PR.

🤖 Generated with Claude Code

Update — additional pre-existing CI breakages folded in (seroval lockfile sync)

After pushing the simple-git fix, CI surfaced additional pre-existing main-level breakages that had been masked by the audit failure: npm ci was failing in both tanstack-start-ui/ and react-apollo-ui/ with:

npm error Invalid: lock file's seroval@1.5.2 does not satisfy seroval@1.5.4
npm error Invalid: lock file's seroval-plugins@1.5.2 does not satisfy seroval-plugins@1.5.4

npm install in each of those directories regenerates their lockfiles to 1.5.4 for both packages. Folded into this PR because (a) they're the same shape of pre-existing main breakage and (b) all three must land before any open PR can pass CI. PRs #305 and #306 are blocked on this PR landing.

Commits in this PR:

  • 9331aa9 fix(deps): bump simple-git in nuxt-api to patch GHSA-hffm-xvc3-vprc
  • 1ade966 fix(deps): sync tanstack-start-ui lockfile (seroval 1.5.2 → 1.5.4)
  • ec44aef fix(deps): sync react-apollo-ui lockfile (seroval 1.5.2 → 1.5.4)

Resolves the high-severity Remote Code Execution advisory by bumping
the transitive simple-git from 3.35.2 to 3.36.0 (via npm audit fix).
Pulled in via nuxt → @nuxt/devtools → simple-git. Other packages in
the monorepo do not depend on simple-git, so no other lockfiles change.

CI's audit:ci:all step was failing on this advisory.
Copilot AI review requested due to automatic review settings May 6, 2026 12:40
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

Files not reviewed (1)
  • nuxt-api/package-lock.json: Language not supported

CI's `cd tanstack-start-ui && npm ci` step has been failing on every PR
against main with:

    npm error Invalid: lock file's seroval@1.5.2 does not satisfy seroval@1.5.4
    npm error Invalid: lock file's seroval-plugins@1.5.2 does not satisfy seroval-plugins@1.5.4

`npm install` in tanstack-start-ui/ regenerates the lockfile to 1.5.4
for both packages, restoring `npm ci` and `audit-ci` to working order.

Folded into this PR (the simple-git fix) because both are pre-existing
main-level CI breakages blocking every open PR; landing them together
unblocks the queue in one go.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
After the previous commit fixed tanstack-start-ui's lockfile, CI surfaced
the same drift in react-apollo-ui — `cd react-apollo-ui && npm ci` was
failing with the same seroval@1.5.2 vs 1.5.4 mismatch. `npm install` in
react-apollo-ui/ regenerates its lockfile to match.

tanstack-ui and nuxt-api both have seroval@1.5.2 in their lockfiles too,
but their package.json constraints accept 1.5.2 cleanly — `npm install`
didn't touch them. Only the two tanstack-start consumers (tanstack-start-ui,
react-apollo-ui) needed bumping.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

Files not reviewed (2)
  • nuxt-api/package-lock.json: Language not supported
  • tanstack-start-ui/package-lock.json: Language not supported

Comment thread nuxt-api/package-lock.json
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

Files not reviewed (3)
  • nuxt-api/package-lock.json: Language not supported
  • react-apollo-ui/package-lock.json: Language not supported
  • tanstack-start-ui/package-lock.json: Language not supported

Comment thread react-apollo-ui/package-lock.json
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

Files not reviewed (3)
  • nuxt-api/package-lock.json: Language not supported
  • react-apollo-ui/package-lock.json: Language not supported
  • tanstack-start-ui/package-lock.json: Language not supported

@WhatIfWeDigDeeper WhatIfWeDigDeeper merged commit 4685b22 into main May 6, 2026
13 checks passed
@WhatIfWeDigDeeper WhatIfWeDigDeeper deleted the fix/bump-simple-git-rce branch May 6, 2026 21:53
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