- 01 Jun, 2026 1 commit
-
-
Sebastian Sebbie Silbermann authored
-
- 31 May, 2026 2 commits
-
-
Luke Sandberg authored
Backports [feat(turbopack): add LocalPathOrProjectPath PostCSS config resolution (#91338)](https://github.com/vercel/next.js/pull/91338) to `next-16-2`. <!-- NEXT_JS_LLM_PR -->
-
Sebastian "Sebbie" Silbermann authored
-
- 28 May, 2026 2 commits
-
-
Tim Neutkens authored
Backports [Propagate adapter preferred regions](https://github.com/vercel/next.js/pull/94123) to `next-16-2`. <!-- NEXT_JS_LLM_PR -->
-
Tim Neutkens authored
Backports [Fix "type: module" in project dir when using standalone or adapters](https://github.com/vercel/next.js/pull/93612) to `next-16-2`. <!-- NEXT_JS_LLM_PR -->
-
- 27 May, 2026 1 commit
-
-
Benjamin Woodruff authored
https://vercel.slack.com/archives/C0B0LKK5QD7/p1779825011578549 > I'm not having any luck reproducing this locally, and there's no useful logs from GitHub Actions. Looking at the timestamps, it successfully completes `pnpm install` and then hangs for 30m until it times out. > I'm not seeing these failures in the `canary` branch, and this only happens with node 24. I'm just going to disable this job on the `next-16-2` branch. The failure doesn't appear to be indicative of any real issue on our end, it's more likely an issue with node or pnpm. Example failure: https://github.com/vercel/next.js/actions/runs/26503905088/job/78051437920
-
- 19 May, 2026 5 commits
-
-
Niklas Mischkulnig authored
Backport of https://github.com/vercel/next.js/issues/91832 For https://github.com/vercel/next.js/issues/93790 and https://github.com/vercel/next.js/issues/92711Co-authored-by:
Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by:
Tobias Koppers <sokra@users.noreply.github.com> Co-authored-by:
Claude <noreply@anthropic.com>
-
Hendrik Liebau authored
Backports: - #93792 Co-authored-by:
Elisha Greenwald <ejgreenwald@gmail.com> Co-authored-by:
LiamBoz <thisamazingnow@gmail.com> Co-authored-by:
kmaclip <kmartclips@proton.me>
-
Hendrik Liebau authored
Backports: - #93617 - #93601 --------- Co-authored-by:
Swarnava Sengupta <swarnava.sengupta@vercel.com> Co-authored-by:
Or Nakash <ornakash@gmail.com>
-
Hendrik Liebau authored
Backports: - #93294
-
Hendrik Liebau authored
Backports: - #92892 - #93486
-
- 18 May, 2026 1 commit
-
-
Hendrik Liebau authored
Backports: - #93802
-
- 12 May, 2026 1 commit
-
-
Joseph authored
## Summary Backports documentation fixes and improvements from canary to the `next-16-2` branch. ### Included commits: - eddbd54f90 docs: clarify that proxy/middleware matches static assets by default (#92441) - 43d1229d4c docs: clarify serverless runtime behavior for use cache (#92232) - 630d9052c6 docs: add note on React canary version to View transitions guide (#92315) - 08f6f62988 docs: note PPR default in cacheComponents reference (#92378) - 07182b567c docs: clarify cacheLife() cannot be called at module scope (#92326) - 7bb8e7de84 docs: add note on installing `server-only` in data security guide (#92445) - 6440b9e11b docs: update details about `unstable_retry()` behavior (#91827) - 246c5e1f5d docs: link updateTag from cacheTag reference (#92379) - a99d7fd16e docs: native db drivers with sync queries (#92572) - aef9105d1b docs: add Link transitionTypes version history (#92624) - db1d2cc398 docs(cli): clarify that `--debug-build-paths` requires route group folders in paths (#92618) - 82f3f48880 docs: fix broken bun.sh Nextjs documentation link (#92698) - 5a1598608e docs: add migration note for experimental cache flags to cacheComponents (#92318) - d1cf752c5d docs: draftMode alignment (#92794) - ccc6d36578 docs: amends to preserving-ui-state guide (#92270) - 44e3208add docs: link Activity guide from Cache Components migration guide (#92571) - 2217cbaa8c docs: add guide for displaying dates without hydration flash (#92786) - d233d05456 docs: remove broken error-handling overlay screenshot (#93279) - 356644ba06 Update 05-server-and-client-components.mdx (#93374) - ae88a95b5e docs: clarify rendering flow in Server/Client interleaving example (#93381) - b4191904d8 docs: clarify proxy runtime history (#93467) - e41fc92a76 docs: remove unreachable forms and mutations (#93509) - 405a912968 docs: broken link from usePathname compat call out (#93528) - 58ea3325f1 docs: escape literal triple-backticks in contribution guide (#93584) - d98ea7cc67 docs: clarify cacheTag limit - it is per call (#93768) - 7988818441 docs: devIndicators with usage example (#93784) --------- Co-authored-by:
Cursor Agent <cursoragent@cursor.com> Co-authored-by:
Joseph <icyJoseph@users.noreply.github.com> Co-authored-by:
MK <135491799+wwenrr@users.noreply.github.com> Co-authored-by:
wwenrr <wwenrr@users.noreply.github.com> Co-authored-by:
Aurora Scharff <66901228+aurorascharff@users.noreply.github.com> Co-authored-by:
vercel[bot] <35613825+vercel[bot]@users.noreply.github.com> Co-authored-by:
Abhishek Mardiya <97448460+abhishekmardiya@users.noreply.github.com> Co-authored-by:
Jiwon Choi <devjiwonchoi@gmail.com> Co-authored-by:
Hamed <55133282+hamedniroomand@users.noreply.github.com> Co-authored-by:
Jimmy Lai <laijimmy0@gmail.com> Co-authored-by:
christopherkindl <53372002+christopherkindl@users.noreply.github.com> Co-authored-by:
Zana Abdi <zana.abdi@hotmail.com> Co-authored-by:
Armando A. Calderón <armandoandrecalderon@gmail.com>
-
- 07 May, 2026 6 commits
-
-
Sebastian "Sebbie" Silbermann authored
-
Tim Neutkens authored
## What? Applies https://github.com/vercel/next.js/commit/d166096c399c4fc4e09cd2d1bf26dca6579a855d for canary and handles the Turbopack-side implementation for `middleware-manifest.json` which is used for edge runtime middleware.ts --------- Co-authored-by:
Zack Tanner <1939140+ztanner@users.noreply.github.com>
-
Tim Neutkens authored
## What? The Turbopack path incorrectly included a double backslash instead of one backslash in the regex matcher.
-
Sebastian "Sebbie" Silbermann authored
Co-authored-by:Matt Mastracci <matthew@mastracci.com>
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
Co-authored-by:
Niklas Mischkulnig <4586894+mischnic@users.noreply.github.com> Co-authored-by:
Tobias Koppers <tobias.koppers@googlemail.com>
-
- 06 May, 2026 14 commits
-
-
Sebastian "Sebbie" Silbermann authored
-
Zack Tanner authored
(cherry picked from commit 807e363b13cc9395aa74f75122d1d16b4a46dc1a)
-
Zack Tanner authored
* fix: proxy should match segment prefetches for canonical urls * include .rsc handling
-
Josh Story authored
This header is used by proxies to perform a concatenating resume render for partial prerendering. It is never sent from the client so we can filter it out when running in a mode that does not have an intermediate proxy.
-
Zack Tanner authored
-
Josh Story authored
we have auditing that server files aren't included in client chunks but the new htmlescape usage in next/script is causing that validation to fail. This refactors the utility into lib/shared
-
JJ Kasper authored
-
JJ Kasper authored
* test: add rewrite request smuggling coverage * router-server: guard upgrade proxy against absolute-url SSRF * test: relax rewrite smuggling socket timeout * router-server: preserve local websocket upgrades
-
JJ Kasper authored
* Fix i18n middleware matching for default-locale data routes * unskip node middleware on deploy
-
Sebastian "Sebbie" Silbermann authored
-
Josh Story authored
props set on a next/script with beforeInteractive are serialized as JSON into an inline script to be exectuted prior to hydration by Next.js. The props were not additionally escaped and if user input was rendered as through a script it could allow fro XSS. This has alwways been true if you pass user input into the script body or via dangerouslySetInnHTML however and it is always the developers responsibility to sanitize user input before rendering. However wherever React has some automatic escaping to act as an additional defense against common mistakes leading to vulnerabilities like XSS Next.js should mirror that becasue from the user's perspective it is not clear that React is not directly rendering the script props and content. This change adds additional escaping so that serialized properties cannot break out of the script scope and execute unexpected payloads.
-
Hendrik Liebau authored
Backports: - #92231 --------- Co-authored-by:
Zack Tanner <1939140+ztanner@users.noreply.github.com> Co-authored-by:
Andrew Clark <git@andrewclark.io>
-
Hendrik Liebau authored
Backports: - #91912 - #93365 --------- Co-authored-by:Sebastian "Sebbie" Silbermann <sebastian.silbermann@vercel.com>
-
Hendrik Liebau authored
Backports: - #93491
-
- 05 May, 2026 2 commits
-
-
Hendrik Liebau authored
-
Josh Story authored
Backport #93453 to 16.2 How was this ever working for dev? In that case, `buildId = "development"` and so it always uses the same cache key Co-authored-by:Niklas Mischkulnig <4586894+mischnic@users.noreply.github.com>
-
- 27 Apr, 2026 5 commits
-
-
Benjamin Woodruff authored
`pnpm dlx` isn't using a lockfile. Using the self-contained binary from GitHub and validate the checksum lets us effectively pin `datadog-ci` and all of its possible transitive dependencies. This is a follow-up for https://vercel.slack.com/archives/C0APPN2LC83/p1775073127894859 (cherry picked from commit 631fae95)
-
Zack Tanner authored
Stacked on https://github.com/vercel/next.js/pull/93245 Commit signing is required for anything that lands on `canary`. Our previous workflow of using a PAT to push a commit no longer works, since that would have been an unsigned commit. In #93245 we switched to an app token for release workflow steps. This continues by: - Telling Lerna to bump packages but not commit - Creating a signed commit with the staged changes via GitHub's API - Then running the publish flow Test Plan: Dry run [here](https://github.com/vercel/next.js/actions/runs/25001287978/job/73211826479) Commit [here](https://github.com/vercel/next.js/commit/3a8456a62b56615e2f8c1d1e6e7b4e14ce89e078) (cherry picked from commit 012fd7df)
-
Zack Tanner authored
Moves all release workflows off of a GH PAT and uses an app with a short-lived token instead. Test Plan: Dry run [here](https://github.com/vercel/next.js/actions/runs/24934593874). However, this workflow is blocked until we figure out commit signing for the bot app. Some options: - The bot account generates a signing key and we use it in CI (not great, bypasses the app) - The org bypasses signature verification for the bot user (also not great, requires an exemption rule) - We need to rework the commit step so Lerna does not do the push, and instead trigger it via the app + GH API. This seems like the best option, will be added in a follow-up PR. Note: `create-release-branch` workflow is broken in its current form, as we will not be restoring administrator privileges to adjust environment settings. This will become a manual step in the future. (cherry picked from commit e69de2ff)
-
Zack Tanner authored
Moves the `environment` into `publishRelease` rather than `trigger_release` since the actual action we want to create environment rules for is the publish step. (cherry picked from commit 2b846de4)
-
Zack Tanner authored
Switches from a long-lived token to trusted publishing OIDC flow. This requires a bump to Node (for feature support). Otherwise just dropping unnecessary envs. (cherry picked from commit 129896c2)
-