Skip to content

fix(deps): bump next, @sentry/nextjs and vite to resolve Dependabot alerts - #9042

Merged
AviPeltz merged 2 commits into
mainfrom
fix/dependabot-2026-10-29
Oct 29, 2026
Merged

AviPeltz merged 2 commits into
mainfrom
fix/dependabot-2026-10-29

Conversation

@AviPeltz

@AviPeltz AviPeltz commented Oct 29, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Bumps 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) and vite 7.3.5 → 7.3.7 (desktop, ui). Lockfile refreshed.

Also bumps @lingui/swc-plugin 6.6.0 → 6.7.1 in the same four Next apps. Next 16.4.1 cannot run 6.6.0 (built for swc_core 66.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 for swc_core 77.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:

Not in this PR:

Note: @sentry/nextjs 10.75 logs a deprecation warning at build time: import withSentryConfig from @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 typecheck in apps/api, docs, marketing, web, desktop and packages/ui
  • bun run build in 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 chunks
  • CI Deploy Preview jobs (API, Web, Marketing, Docs)

Summary by cubic

Bumps next 16.3.8→16.4.1, @sentry/nextjs 10.68.0→10.75.2, and vite 7.3.5→7.3.7 to resolve the outstanding Dependabot alerts, and @lingui/swc-plugin 6.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

  • Critical Next.js unauthenticated RCEs in Image Optimization API (SVG) and use cache typed arrays, plus a DoS in App Router Server Actions.
  • Critical Sentry middleware bypass via the Tunnel route.
  • launch-editor command injection and Vite file-serving / cross-origin issues.

Note: @sentry/nextjs 10.75 logs a build-time deprecation warning to import withSentryConfig from @sentry/nextjs/config; it still works and the warning is removed in v11.

Written for commit 6296a42. Summary will update on new commits.

View guided diff Turn on auto-fix

Summary by CodeRabbit

  • Chores
    • Updated the frameworks and development tools used across the API, web, documentation, marketing, desktop, and shared UI applications.
    • Updates include application frameworks, monitoring integrations, localization and build tooling, and development servers.
    • No direct changes to user-facing functionality or behavior are noted in this update. These updates are internal and do not add or remove product capabilities.

…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.
@coderabbitai

coderabbitai Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

Walkthrough

Package manifests update Next.js, Sentry, Lingui, and Vite dependency versions across the root and application packages.

Changes: Dependency version updates

Layer / File(s) Summary
Application dependency versions
package.json, apps/api/package.json, apps/docs/package.json, apps/marketing/package.json, apps/web/package.json
Next.js changes from 16.3.8 to 16.4.1, Sentry from 10.68.0 to 10.75.2, and Lingui from 6.6.0 to 6.7.1 across the listed manifests.
Vite version updates
apps/desktop/package.json, packages/ui/package.json
Vite changes from 7.3.5 to 7.3.7.

Priority: Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: kitenite, saddlepaddle

Merge Risk: Minimal · up to 6296a

The supplied evidence identifies no merge-blocking impact from the dependency upgrades.

Pre-merge checks: Passed 5
Check name Status Explanation
Title check Passed The title clearly identifies the dependency updates and the security-alert remediation. It is concise and uses conventional commit format.
Description check Passed The description provides the change summary, rationale, affected dependencies, resolved and excluded alerts, testing details, known deprecation warning, and remaining unchecked CI tests. It uses equiv…
Linked Issues check Passed The only linked issue is #397 ("chore(desktop): bump version to 0.0.25"). It is closed and completed. It supplies background only. No active directly linked target remains. No linked-issue coding requ…
Out of Scope Changes check Passed With no active linked issue, scope is judged against the PR objectives and the current PR description. The reviewed package.json changes match the stated objectives. next 16.3.8 to 16.4.1 appears in t…
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Full details: Description check

Explanation

The description provides the change summary, rationale, affected dependencies, resolved and excluded alerts, testing details, known deprecation warning, and remaining unchecked CI tests. It uses equivalent headings instead of the template headings but is substantially complete.

Full details: Linked Issues check

Explanation

The only linked issue is #397 ("chore(desktop): bump version to 0.0.25"). It is closed and completed. It supplies background only. No active directly linked target remains. No linked-issue coding requirements apply. The package.json changes in this PR do not change the desktop app version. This absence is not a failure, because #397 is not an active requirement. The current PR objectives also state that no active linked issue targets remain.

Full details: Out of Scope Changes check

Explanation

With no active linked issue, scope is judged against the PR objectives and the current PR description. The reviewed package.json changes match the stated objectives. next 16.3.8 to 16.4.1 appears in the root, apps/api, apps/docs, apps/marketing, and apps/web manifests. @sentry/nextjs 10.68.0 to 10.75.2 appears in apps/api, apps/docs, apps/marketing, and apps/web. vite 7.3.5 to 7.3.7 appears in apps/desktop and packages/ui. @lingui/swc-plugin 6.6.0 to 6.7.1 appears in apps/api, apps/docs, apps/marketing, and apps/web. The description states that the swc-plugin bump is required for Next 16.4.1 to run. No source change outside dependency manifests appears in the summary. bun.lock is excluded by the ignored_files rule, so lockfile content was not inspected. This does not affect the verdict, because the manifest changes alone account for the stated objectives.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (6 skipped: 6 unsupported.)

Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

@greptile-apps

greptile-apps Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[High impact] The reviewed changes appear safe to merge; no actionable defects were found.

Summary

Updates dependency pins across the Next apps, desktop app, and shared UI package.

  • The Next.js apps use updated Next.js and Sentry releases.
  • The Next.js apps use a Lingui plugin built for the newer compiler.
  • Desktop and shared UI use the updated Vite release.
  • Bun’s lockfile records extra package entries from the dependency refresh.

Reviews (1) · Last reviewed commit: "fix(deps): bump next, @sentry/nextjs and..." · Reviewed by Greptile

@github-actions

github-actions Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

🧹 Preview Cleanup Complete

The following preview resources have been cleaned up:

  • ✅ Neon database branch

Thank you for your contribution! 🎉

…0-29

# Conflicts:
#	apps/api/package.json
#	apps/marketing/package.json
#	bun.lock
@AviPeltz
AviPeltz merged commit a0d4b79 into main Oct 29, 2026
18 checks passed
saddlepaddle added a commit that referenced this pull request Nov 2, 2026
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.

This branch was previously deployed

1 inactive deployment
preview — 6296a421 Deployed Oct 29, 2026 by AviPeltz via Deploy API #13249
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.

1 participant