Skip to content

fix(security): raise vite 8.x floor to >=8.0.16 across scenario workspaces#709

Merged
drewdrewthis merged 1 commit into
mainfrom
security/scenario-vite-8.0.16
Jun 26, 2026
Merged

fix(security): raise vite 8.x floor to >=8.0.16 across scenario workspaces#709
drewdrewthis merged 1 commit into
mainfrom
security/scenario-vite-8.0.16

Conversation

@langwatch-agent

Copy link
Copy Markdown
Contributor

Floors the vite 8.x line to >=8.0.16 across the workspaces whose locks had landed on a vulnerable 8.0.x (docs 8.0.10, javascript 8.0.14, template 8.0.10). The existing overrides only floored the 6.x (docs) and 7.x (javascript) lines, leaving the 8.x alerts open. Resolves to 8.1.0 (the current 8.x; the consumer ranges are ^8, and 8.1.0 is past the 8.0.15 vulnerable ceiling).

Alerts resolved

Changes

  • docs/pnpm-workspace.yaml, javascript/package.json (pnpm.overrides), template/package.json (npm + pnpm overrides): added vite@>=8.0.0 <8.0.16 -> >=8.0.16. Template direct dep vite ^8.0.10 -> ^8.0.16.
  • Locks regenerated; the only non-vite additions are vite 8.1.0's rolldown bundler subtree (rolldown/@rolldown/@oxc/@emnapi/tinyglobby). No unrelated drift.

Verification

  • javascript: tsc --noEmit clean, tsup build clean, 150 unit tests pass on vite 8.1.0.
  • pnpm install --frozen-lockfile clean in docs/javascript/template; npm ci clean for the template.
  • scenario has no cooldown; no committed policy touched.

…paces

Floors the vite 8.x line to >=8.0.16 (resolves to 8.1.0) in docs,
javascript and the lovable_clone template (pnpm + npm locks), closing the
HIGH and MODERATE vite advisories. The existing 6.x/7.x vite overrides did
not cover the 8.x line that these locks had landed on (8.0.10 / 8.0.14).

Patch/minor within the existing major. Dogfooded: javascript typecheck +
tsup build + 150 unit tests pass on vite 8.1.0; frozen install clean in
docs/javascript/template and npm ci clean for the template.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 26, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 099bc23b-7adf-4c5e-b108-7715107cc07b

📥 Commits

Reviewing files that changed from the base of the PR and between 0e12e59 and 98839cf.

⛔ Files ignored due to path filters (4)
  • docs/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
  • javascript/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
  • python/examples/lovable_clone/template/package-lock.json is excluded by !**/package-lock.json
  • python/examples/lovable_clone/template/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (3)
  • docs/pnpm-workspace.yaml
  • javascript/package.json
  • python/examples/lovable_clone/template/package.json

Walkthrough

The PR updates Vite version constraints in the docs workspace, JavaScript package, and Python example template. The template also bumps its Vite devDependency to ^8.0.16 and adds matching override rules.

Changes

Vite override alignment

Layer / File(s) Summary
Shared workspace overrides
docs/pnpm-workspace.yaml, javascript/package.json
Both manifests add or update the vite@>=8.0.0 <8.0.16 override to resolve to >=8.0.16.
Example template package
python/examples/lovable_clone/template/package.json
The template bumps the Vite devDependency to ^8.0.16 and adds matching override rules in both overrides and pnpm.overrides.

Suggested reviewers

  • sergioestebance

Poem

I nibbled the Vite carrots bright,
And nudged the versions up just right.
Workspace hops, templates align,
Now every manifest's in line. 🐇
Thump-thump!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly states the main change: raising the Vite 8.x floor across scenario workspaces for security.
Description check ✅ Passed The description matches the changeset and accurately summarizes the Vite override and dependency updates.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch security/scenario-vite-8.0.16

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown
Contributor

Automated low-risk assessment

This PR was evaluated against the repository's Low-Risk Pull Requests procedure and does not qualify as low risk.

This PR's diff could not be evaluated automatically: Diff too large for automated evaluation (102041 chars exceeds 100000-char limit). Manual review required.

This PR requires a manual review before merging.

@langwatch-agent

Copy link
Copy Markdown
Contributor Author

CI is green across the board (typecheck, tsup build, vitest, frozen installs, template npm ci). Ready for human review and merge.

@drewdrewthis
drewdrewthis merged commit 42d877e into main Jun 26, 2026
18 checks passed
@drewdrewthis
drewdrewthis deleted the security/scenario-vite-8.0.16 branch June 26, 2026 08:06
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