[dependabot]

Bumps vite from 7.3.6 to 7.3.7.

Release notes

Sourced from vite's releases.

v7.3.7

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

7.3.7 (2026-10-06)

Bug Fixes

• deps: update launch-editor to v2.14.2 (#23654) (a0a3339)
• html: filename passed to transformIndexHtml should not include queries (#23653) (8d479f9)
• server: store ids to safeModulePaths rather than URLs (#23656) (f0d76c7)

Commits

• 284f6b5 release: v7.3.7
• f0d76c7 fix(server): store ids to safeModulePaths rather than URLs (#23656)
• a0a3339 fix(deps): update launch-editor to v2.14.2 (#23654)
• 8d479f9 fix(html): filename passed to transformIndexHtml should not include queries (...
• See full diff in compare view

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-changelog	Ready	Preview	Oct 23, 2026 7:58pm UTC

[cursor]

The change patches the test bundler only. Public pages should keep the same behavior. An issue escalates when page visits fall or production errors rise.

Services: sentry-changelog.

Mention @change-monitor in a comment to update the plan.

Plan

What changed

Tests now bundle with Vite 7.3.7 instead of Vite 7.3.6. Production still compiles with Next.js. Public pages keep the same HTML and JS on purpose. sentry-changelog must deploy for this lockfile to reach production. The Vercel report workflow and the Sentry application key both name this service.

Risk

A failed install can stop the Vercel build. A bad client bundle can throw new JavaScript errors on public pages. Vite does not compile production assets. The next production deploy still rebuilds the app. Users would see blank pages or failed changelog loads. Server Action mismatch errors already rise around deploys. Treat a short spike of that title as deploy noise.

Intended effect

This patch has no queryable production effect. Vite 7.3.7 only bundles Vitest. No new counter exists. Mark intended_effect unknown. Do not mark it absent because page visits continue.

Regression watch

A bad production bundle can break changelog page loads. Watch these four signals. Compare each one to the band from the two sampled days. Escalate when a signal leaves its band. After deploy, a short rise in Server Action mismatch errors is expected. Do not count that title as this patch.

The Server Action title is Error: Failed to find Server Action. This request might be from an older or newer deployment. Last day that title was 43 of 49 production errors. The other six were Changelog SQL failures and MDX compile errors.

Signal	Baseline	Window	Rule	Source
page_visit TPM	16.3-16.9 visits per minute	2026-10-21T12:42:00Z to 2026-10-23T12:42:00Z	Hold inside the band. Escalate if the rate falls below 16.3. The rate may vary by weekday.	Sentry org sentry project changelog. Query metric.name:page_visit AND sentry.environment:production. 24h sum 24363. Prior 24h sum 23412.
Changelog server span failure rate	0.07-0.11%	2026-10-21T12:42:00Z to 2026-10-23T12:42:00Z	Hold inside the band. Escalate if the rate rises above 0.11%.	Sentry org sentry project changelog. Query span.kind:server AND url.full:"*/changelog*" AND sentry.environment:production. 24h count 41850, failure rate 0.11%, p95 791ms. 2d pooled count 80781, failure rate 0.07%, p95 814ms.
Other production errors as a share of page_visit	0.008-0.025%	2026-10-21T12:42:00Z to 2026-10-23T12:42:00Z	Hold inside the band. Escalate if the share rises above 0.025%. Exclude the Server Action title. Last 24h had 6 other errors. Prior 24h had 2. Last 7d had 100 production errors in total.	Sentry org sentry project changelog. Query environment:production on error events. Group by title. Drop the Server Action title. Divide the rest by page_visit.
platform:javascript errors	0 events	2026-10-22T12:42:00Z to 2026-10-23T12:42:00Z	Hold at 0. Escalate if any javascript-platform error appears. Last 24h all 49 errors used platform node.	Sentry org sentry project changelog. Query environment:production AND platform:javascript.

Not observable

Vitest pass or fail does not appear in Sentry. Vite does not run on production requests. There is no pre-ship rate for a Vite path in production. Web vitals were not sampled for this plan.