Skip to content

chore(deps): bump vite to 6.4.6 in docs and starters (GHSA-p4f5-76q4-ffq7) - #52

Merged
tiagosiebler merged 3 commits into
sieblyio:mainfrom
JJ-Cro:update16112026
Nov 18, 2026
Merged

tiagosiebler merged 3 commits into
sieblyio:mainfrom
JJ-Cro:update16112026

Conversation

@JJ-Cro

@JJ-Cro JJ-Cro commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

Summary

Move the docs site and all starters off vite 5.4.21 to 6.4.6 to patch GHSA-p4f5-76q4-ffq7 (vite dev-server RCE). The 5.4.x line has no patched release.

Changelog

  • Pin vite 6.4.6 in the root package and all 20 starters/*/{vite,react} packages (incl. the new gateio, htx and kucoin starters)
  • Override VitePress's vite dependency to the root version; refresh the root lockfile
  • Starter generator (compatibility/config.mjs) and compatibility report text now use vite 6.4.6
  • @vitejs/plugin-react 4.7.0 already supports vite 6; no starter code changes

Checks

  • npm ci, npm ls vite (6.4.6 only), npm run build:release, npm run build, npm run check, npm run check:public, npm run check:starters and the other check scripts: pass
  • All 20 starters: npm install + npm run build: pass

…ffq7)

- Pin vite 6.4.6 in the docs site and all 14 vite/react starters (5.4.x has no patched release)
- Override VitePress's vite dependency to the root vite version and refresh the lockfile
- Update the starter generator's vite version
…HSA-p4f5-76q4-ffq7)

- Pin vite 6.4.6 in starters/{gateio,htx,kucoin}/{vite,react}, added upstream after the first bump
- Compatibility report text: tested with Vite 6.4.6

@tiagosiebler tiagosiebler left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM, thanks

@tiagosiebler
tiagosiebler merged commit 59b3a6f into sieblyio:main Nov 18, 2026
2 checks passed
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