Skip to content

Bump @tanstack/react-start from 1.168.32 to 1.168.60 in site - #17

Open
katsugtgz wants to merge 1 commit into
edaywalid:mainfrom
katsugtgz:dep-bump-tanstack-react-start
Open

katsugtgz wants to merge 1 commit into
edaywalid:mainfrom
katsugtgz:dep-bump-tanstack-react-start

Conversation

@katsugtgz

Copy link
Copy Markdown

Updates @tanstack/react-start to address GHSA-qx66-fv34-fjm8 (CVE-2026-102989).

Evidence:

  • site/package-lock.json referenced @tanstack/react-start@1.168.32 and @tanstack/start-server-core@1.169.17
  • osv-scanner reported GHSA-qx66-fv34-fjm8 on both packages before the update
  • updated versions: @tanstack/react-start@1.168.60, @tanstack/start-server-core@1.169.39

Validation:

  • npm run build passes in site/ (vite build and prerender, run before and after the change)
  • osv-scanner reports zero advisories on the full lockfile after the update

The same resolution also clears the other findings that were present: seroval 1.5.6 (GHSA-jp82-f5mq-hwhp, GHSA-p6vx-979v-rg4c), js-yaml 4.3.0 (GHSA-2883-xcg3-v3hh, GHSA-5p4m-2wfm-xmqj), nanoid 3.3.16 (GHSA-2v37-7h3g-55p8), source-map-js 1.2.1 (GHSA-68fv-2mgg-jv7q).

The make test commands in CONTRIBUTING cover the Go CLI; this change only touches the site/ web subtree, so validation there is the site build plus the lockfile scan.

Scope: dependency and lockfile update only (site/package.json, site/package-lock.json).

Clears GHSA-qx66-fv34-fjm8 (CVE-2026-102989) on @tanstack/react-start
and @tanstack/start-server-core, plus seroval, js-yaml, nanoid, and
source-map-js advisories. osv-scanner is clean on the full lockfile.
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