fix(deps): upgrade Next.js to 16.3.3 for PROD-5209 - #205
Merged
michaeljguarino merged 2 commits intoSep 14, 2026
Merged
Conversation
Contributor
Author
There was a problem hiding this comment.
This PR was generated by the codex Plural Agent Runtime. Here's some useful information you might want to know to evaluate the ai's perfomance:
| Name | Details |
|---|---|
| 💬 Prompt | Remediate PROD-5209 in this repository and create exactly one PR.... |
| 🔗 Run history | View run history |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Contributor
Author
There was a problem hiding this comment.
✅ Deploy preview for marketing-pr-205 is ready!
| Name | Details |
|---|---|
| ⚡ Service | marketing-pr-205 (5 / 5 ready) |
| ☁️ Cluster | plural (eks) |
| 4d0a650 | |
| https://console.mgmt.plural.sh/cd/clusters/446acdef-8524-425a-a49f-5336a... | |
| 🔍 Logs URL | https://console.mgmt.plural.sh/cd/clusters/446acdef-8524-425a-a49f-5336a... |
| 🌊 Flow URL | https://console.mgmt.plural.sh/flows/fbbadfa5-fa67-4c16-ab32-42dca133aa3... |
| Preview Link | Preview |
You can learn more about preview environments and Plural Flows here
Member
|
we should add a skill in this repo that any pr that needs e2e testing should include this annotation in the pr body: |
michaeljguarino
approved these changes
Sep 14, 2026
michaeljguarino
deleted the
agent/fix-prod-5209-next-16-3-3-1789353126730
branch
September 14, 2026 03:03
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the direct runtime Next.js dependency to the vendor-fixed Next 16 release for PROD-5209.
Security remediation
Dependency changes
next: 16.2.11 → 16.3.3 (exact declaration and resolved lockfile version).@next/third-parties: 16.2.11 → 16.3.3 to remain aligned with the Next 16 release.package-lock.jsonwith npm 11.19.1 using npm; no integrity or resolution data was manually edited.@next/envand all Next SWC platform packages to 16.3.3, and updates transitive@swc/helpersfrom 0.5.19 to 0.5.23.AVIF assessment
next.config.tscontains noimages,avif,webp, image loader, remote-pattern, or image-domain configuration, and no other relevant image configuration is present. No configuration change was made: upgrading to the vendor-fixed Next.js release is the required remediation, and AVIF was not disabled or otherwise altered as a workaround.Validation
All commands passed in
node:26-alpine3.24:npm ci --ignore-scriptsnpm run lint./node_modules/.bin/next buildnpm ls next @next/third-parties --depth=0(both resolve to 16.3.3)git diff --checkThe production build exited successfully. It emitted two non-blocking Turbopack dynamic-filesystem tracing warnings for
src/app/slice-library/page.tsx.Plural Flow: marketing
Plural Preview: marketing
Fixes PROD-5209