Skip to content

[pull] canary from vercel:canary#1112

Merged
pull[bot] merged 5 commits into
code:canaryfrom
vercel:canary
Jun 8, 2026
Merged

[pull] canary from vercel:canary#1112
pull[bot] merged 5 commits into
code:canaryfrom
vercel:canary

Conversation

@pull

@pull pull Bot commented Jun 8, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

aurorascharff and others added 5 commits June 8, 2026 14:09
### What?

Adds an `updateTag` example to the `cacheTag` API reference page.

### Why?

The `cacheTag` docs only showed `revalidateTag` for cache invalidation.
For forms and user-triggered mutations (the dominant use case for
`cacheTag`), `updateTag` is the recommended API because it provides
read-your-own-writes semantics. DX agent friction logs showed agents
defaulting to `revalidateTag` and hitting the deprecated single-arg
error before discovering `updateTag` via web search.

### How?

Added a second example block after the existing `revalidateTag` one,
showing `updateTag('my-data')` in a Server Function.

Co-authored-by: Joseph Chamochumbi <joseph.chamochumbi@vercel.com>
### What?

Remove `experimental.useNodeStreams` from the public config surface and
make Node streams always-on for Node.js App Router rendering.

The smaller default-on change and dedicated CI cleanup landed in #94311.
The standalone compatibility update landed separately in #94347.

### Why?

Node streams are now the default Node.js runtime rendering path, so the
opt-in config and runtime selection plumbing are stale. Edge bundles
continue to use the web-stream path because Node streams are unavailable
there.

### How?

- Define `__NEXT_USE_NODE_STREAMS` as true for Node.js app runtime
bundles and false for edge user bundles.
- Remove config, schema, runtime, export, and server plumbing for
`experimental.useNodeStreams`.
- Delete the obsolete env-precedence fixture.
- Clean benchmark docs and scripts that still set or compare
`experimental.useNodeStreams`.

### Verification

- `pnpm --filter=next types`
- `pnpm build-all`

<!-- NEXT_JS_LLM_PR -->
### What?

Remove the cacheComponents + web streams rendering branches from
`app-render`.

### Why?

`cacheComponents` does not support the edge runtime, and Node streams
are now always-on for the Node.js runtime in the parent PR. That makes
the cacheComponents web-stream branches dead code.

### How?

- Collapse cacheComponents staged RSC rendering to the Node-stream
implementation.
- Remove the web-stream cacheComponents helper functions and
static-stage byte counter.
- Keep the ordinary non-cacheComponents web-stream paths for
edge/runtime compatibility.

### Verification

- `pnpm --filter=next types`
- `pnpm --filter=next build`
- `pnpm test-start-webpack test/e2e/app-dir/app/standalone.test.ts`

<!-- NEXT_JS_LLM_PR -->
### What?

Reduce the `test-new-tests-dev` and `test-new-tests-start` workflow
matrices from ten groups to five.

### Why?

Restore these flake-detection jobs to five concurrent shards.

### How?

Change each matrix group list from `1/10` through `10/10` to `1/5`
through `5/5`.

### Verification

- `pnpm prettier --with-node-modules --ignore-path .prettierignore
--check .github/workflows/build_and_test.yml`
- `git diff --cached --check`

<!-- NEXT_JS_LLM_PR -->
@pull pull Bot locked and limited conversation to collaborators Jun 8, 2026
@pull pull Bot added the ⤵️ pull label Jun 8, 2026
@pull pull Bot merged commit c082ffe into code:canary Jun 8, 2026
2 of 3 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants