Repository navigation
fix(deps): bump next, @sentry/nextjs and vite to resolve Dependabot alerts - #9042
Conversation
…lerts next 16.3.8 -> 16.4.1 (root override, api, docs, marketing, web), @sentry/nextjs 10.68.0 -> 10.75.2 (api, docs, marketing, web), vite 7.3.5 -> 7.3.7 (desktop, ui). next 16.4.1 cannot run @lingui/swc-plugin 6.6.0 (built for swc_core 66.0.3): Turbopack fails with "Failed to deserialize program received from host". Bump the plugin to 6.7.1 (swc_core 77.1.1) in the same four Next apps.
Walkthrough
Merge Risk:
|
[High impact] The reviewed changes appear safe to merge; no actionable defects were found. SummaryUpdates dependency pins across the Next apps, desktop app, and shared UI package.
Reviews (1) · Last reviewed commit: "fix(deps): bump next, @sentry/nextjs and..." · Reviewed by Greptile |
🧹 Preview Cleanup CompleteThe following preview resources have been cleaned up:
Thank you for your contribution! 🎉 |
…0-29 # Conflicts: # apps/api/package.json # apps/marketing/package.json # bun.lock
Sentry keeps its client under `__SENTRY__[SDK_VERSION]`. #9042 moved the API to @sentry/nextjs 10.75.2 but left packages/trpc on @sentry/core 10.68.0, so every span and captureException from trpc code running in the API has looked in an empty carrier and done nothing since 2026-10-29: the provision job's trace, the cloud-workspace start trace, and the exceptions meter.ts and wake.ts report.
Summary
Bumps
next16.3.8 → 16.4.1 (root override + api, docs, marketing, web),@sentry/nextjs10.68.0 → 10.75.2 (api, docs, marketing, web) andvite7.3.5 → 7.3.7 (desktop, ui). Lockfile refreshed.Also bumps
@lingui/swc-plugin6.6.0 → 6.7.1 in the same four Next apps. Next 16.4.1 cannot run 6.6.0 (built forswc_core66.0.3): the Deploy jobs on #8821 failed with "Failed to execute @lingui/swc-plugin … Failed to deserialize program received from host". 6.7.x is built forswc_core77.1.1 (see the plugin README's compatibility table).This replaces #8821 (same bumps, without the swc-plugin fix; also conflicts with main) and the per-directory Dependabot PRs #8810, #8808, #8738 and #8694.
Alerts resolved:
use cachefunctions returning typed arraysfs.existsSync()existence check can be bypassed on Windows (via vite)server.fs.allowcould be served when project paths match system paths on non-Windows machineNot in this PR:
@modelcontextprotocol/sdk, hono: covered by fix(deps): bump storybook, @modelcontextprotocol/sdk and hono in every workspace to resolve Dependabot alerts #8903 (green, but conflicts with main).@azure/msal-node(Update finding Claude #444): covered by Dependabot PR chore(deps): bump @azure/msal-node from 5.5.0 to 7.1.0 in /packages/trpc #8836.Note:
@sentry/nextjs10.75 logs a deprecation warning at build time: importwithSentryConfigfrom@sentry/nextjs/config. It still works and goes away in v11.Test plan
bun install(Bun 1.4.3)bun run lint:fix(clean, no fixes)bunx sherif(no issues)bun run typecheckin apps/api, docs, marketing, web, desktop and packages/uibun run buildin apps/docs (Next 16.4.1 + Turbopack + swc-plugin 6.7.1): compiled, 244/244 static pages, no SWC plugin errors, no macro imports left in the compiled chunksSummary by cubic
Bumps
next16.3.8→16.4.1,@sentry/nextjs10.68.0→10.75.2, andvite7.3.5→7.3.7 to resolve the outstanding Dependabot alerts, and@lingui/swc-plugin6.6.0→6.7.1 because Next 16.4.1 can't run the old plugin — Turbopack builds fail with a deserialization error.Alerts resolved
use cachetyped arrays, plus a DoS in App Router Server Actions.launch-editorcommand injection and Vite file-serving / cross-origin issues.Note:
@sentry/nextjs10.75 logs a build-time deprecation warning to importwithSentryConfigfrom@sentry/nextjs/config; it still works and the warning is removed in v11.Written for commit 6296a42. Summary will update on new commits.
Summary by CodeRabbit