fix(frontend): bump vite to 7.3.6 in lockfile to fix npm ci#366
Conversation
vite@7.3.6 was published 2026-06-25; the root package-lock.json still pinned 7.3.5, so `npm ci` failed repo-wide on all frontend CI jobs ("lock file's vite@7.3.5 does not satisfy vite@7.3.6"). develop's last green frontend run predated the 7.3.6 publish; every new run (and every open PR) now hits this.
Regenerated with `npm install --package-lock-only` — the only change is vite's version/resolved/integrity (and vite 7.3.6's own widened esbuild range). No other packages, no re-hoisting.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|



Problem
vite@7.3.6was published to npm on 2026-06-25 (~01:51 UTC). The rootpackage-lock.jsonstill pinnedvite@7.3.5, sonpm cinow fails repo-wide on every frontend CI job:develop's last green
test-frontendrun (2026-06-24T18:03Z) predated the 7.3.6 publish; every new run — and every open PR — now hits this. It is unrelated to any one PR's code.Fix
Regenerated the lockfile with
npm install --package-lock-only. The diff is a single entry: vite7.3.5 → 7.3.6(version/resolved/integrity), plus vite 7.3.6's own widenedesbuildrange. No other packages changed, no re-hoisting — both frontend workspaces declare^7.3.5, which7.3.6satisfies.Unblocks
developand all open PRs (incl. #365).🤖 Generated with Claude Code