Backport #3071: fix: upgrade next to 16.2.11 to address CVE-2026-64641#3073
Merged
Conversation
Signed-off-by: Nathan Rajlich <n@n8.io>
🦋 Changeset detectedLatest commit: 99afd7b The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
VaguelySerious
approved these changes
Jul 23, 2026
Contributor
Author
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests▲ Vercel Production (1 failed)fastify (1 failed):
🌍 Community Worlds (101 failed)redis (18 failed):
turso (83 failed):
Details by Category❌ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
❌ 🌍 Community Worlds
✅ 📋 Other
❌ Some E2E test jobs failed:
Check the workflow run for details. |
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
…ed to 0.56.0, whose restructured ESM export paths break the deep imports `monaco-vim@0.4.4` relies on, failing the Turbopack production build.
This commit fixes the issue reported at workbench/swc-playground/package.json:21
## Bug
`workbench/swc-playground/package.json` declared `"monaco-editor": "latest"`. When this PR bumped `next` (`16.2.1` → `16.2.11`) in the same `package.json`, pnpm re-resolved the lockfile and the floating `latest` spec for `monaco-editor` drifted from `0.55.1` to `0.56.0`.
The build log confirms this in the install phase:
```
- monaco-editor 0.55.1
+ monaco-editor 0.56.0
```
`monaco-editor@0.56.0` restructured its ESM export paths, so the deep imports that `monaco-vim@0.4.4` performs no longer resolve, and the Turbopack production build fails:
```
./node_modules/.pnpm/monaco-vim@0.4.4_monaco-editor@0.56.0/node_modules/monaco-vim/dist/index.mjs
Module not found: Can't resolve 'monaco-editor/esm/vs/editor/common/commands/shiftCommand'
Module not found: Can't resolve 'monaco-editor/esm/vs/editor/editor.api'
```
`monaco-vim` is pulled in through `workbench/swc-playground/components/editor.tsx` (dynamic `import('monaco-vim')` for vim mode).
### Trigger
Any production build of the `workflow-sdk-compiler-playground` app with the re-resolved lockfile: `next build` → Turbopack tries to bundle `monaco-vim@0.4.4`, whose `monaco-editor/esm/...` deep imports don't exist in `0.56.0`. The parent commit (before this PR) resolved `monaco-editor@0.55.1` and built fine, so this is a regression introduced purely by the lockfile re-resolution.
## Fix
1. Pinned `"monaco-editor": "0.55.1"` in `workbench/swc-playground/package.json` (the previously-working version that provides the ESM paths `monaco-vim@0.4.4` expects).
2. Regenerated `pnpm-lock.yaml` (`pnpm install --lockfile-only`), which reverts `monaco-editor` back to `0.55.1` everywhere (importer spec/version, `@monaco-editor/react` and `monaco-vim` peer resolutions, and the package/snapshot entries).
The lockfile diff is cleanly scoped: only `monaco-editor` and its legitimately version-tied transitive dependency `dompurify` change (`0.55.1` uses `dompurify@3.2.7` vs `0.56.0`'s `dompurify@3.4.8`), exactly matching the pre-regression lockfile state. No unrelated packages were touched.
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Co-authored-by: VaguelySerious <mittgfu@gmail.com>
VaguelySerious
disabled auto-merge
July 23, 2026 22:45
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
1 participant
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.
Automated backport of #3071 to
stable(backport job run).AI recommendation: This is a security-driven dependency bump (next → 16.2.11 for CVE-2026-64641) touching
packages/nextand workbench apps that exist onstable, which squarely matches the backport criteria for dependency bumps and fixes affecting both branches. The onlystable-unmaintained file touched isdocs/package.json, which the backport tooling auto-resolves in favor ofstable.Merge conflicts were resolved by AI (opencode with
anthropic/claude-fable-5). Please review the conflict resolution carefully before merging.