This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @vercel/backends@0.0.40

### Patch Changes

- Updated dependencies
\[[`9721f4948a72d273f792c54f5393aa50ac279209`](9721f49)]:
    -   @vercel/build-utils@13.6.2

## @vercel/build-utils@13.6.2

### Patch Changes

- add partialFallback flag to prerender output
([#14703](#14703))

## @vercel/cervel@0.0.27

### Patch Changes

-   Updated dependencies \[]:
    -   @vercel/backends@0.0.40

## vercel@50.25.6

### Patch Changes

- Updated dependencies
\[[`9721f4948a72d273f792c54f5393aa50ac279209`](9721f49)]:
    -   @vercel/build-utils@13.6.2
    -   @vercel/next@4.15.37
    -   @vercel/backends@0.0.40
    -   @vercel/elysia@0.1.43
    -   @vercel/express@0.1.52
    -   @vercel/fastify@0.1.46
    -   @vercel/go@3.4.3
    -   @vercel/h3@0.1.52
    -   @vercel/hono@0.2.46
    -   @vercel/hydrogen@1.3.5
    -   @vercel/koa@0.1.26
    -   @vercel/nestjs@0.2.47
    -   @vercel/node@5.6.10
    -   @vercel/python@6.19.0
    -   @vercel/redwood@2.4.9
    -   @vercel/remix-builder@5.6.0
    -   @vercel/ruby@2.3.2
    -   @vercel/rust@1.0.5
    -   @vercel/static-build@2.8.44

## @vercel/client@17.2.51

### Patch Changes

- Updated dependencies
\[[`9721f4948a72d273f792c54f5393aa50ac279209`](9721f49)]:
    -   @vercel/build-utils@13.6.2

## @vercel/elysia@0.1.43

### Patch Changes

-   Updated dependencies \[]:
    -   @vercel/node@5.6.10

## @vercel/express@0.1.52

### Patch Changes

-   Updated dependencies \[]:
    -   @vercel/node@5.6.10
    -   @vercel/cervel@0.0.27

## @vercel/fastify@0.1.46

### Patch Changes

-   Updated dependencies \[]:
    -   @vercel/node@5.6.10

## @vercel/fs-detectors@5.8.15

### Patch Changes

- Fix App Router dynamic API routes returning 404 in production. When a
project has both Next.js (App Router) and a root `api/` folder,
zero-config added a catch-all `^/api(/.*)?# @vercel/fs-detectors → 404
in the filesystem phase, which runs before the rewrite phase where
Next.js routes live. So requests like
`/api/flow/hello/next`or`/api/blog/posts/5`matched the catch-all and
never reached the Next.js route. When Next.js is the frontend we no
longer add that rewrite so those routes are handled by Next.js.
(Locally, only`next dev`worked;`vc dev\` had the same 404.)
([#15297](#15297))

## @vercel/gatsby-plugin-vercel-builder@2.0.142

### Patch Changes

- Updated dependencies
\[[`9721f4948a72d273f792c54f5393aa50ac279209`](9721f49)]:
    -   @vercel/build-utils@13.6.2

## @vercel/h3@0.1.52

### Patch Changes

-   Updated dependencies \[]:
    -   @vercel/node@5.6.10

## @vercel/hono@0.2.46

### Patch Changes

-   Updated dependencies \[]:
    -   @vercel/node@5.6.10

## @vercel/koa@0.1.26

### Patch Changes

-   Updated dependencies \[]:
    -   @vercel/node@5.6.10

## @vercel/nestjs@0.2.47

### Patch Changes

-   Updated dependencies \[]:
    -   @vercel/node@5.6.10

## @vercel/next@4.15.37

### Patch Changes

- add partialFallback flag to prerender output
([#14703](#14703))

## @vercel/node@5.6.10

### Patch Changes

- Updated dependencies
\[[`9721f4948a72d273f792c54f5393aa50ac279209`](9721f49)]:
    -   @vercel/build-utils@13.6.2

## @vercel/static-build@2.8.44

### Patch Changes

-   Updated dependencies \[]:
    -   @vercel/gatsby-plugin-vercel-builder@2.0.142


<!-- VADE_RISK_START -->
> [!NOTE]
> Low Risk Change
>
> This PR is an automated Changesets release that only bumps version
numbers in package.json files and updates CHANGELOG.md files across
multiple packages, with no code logic changes.
> 
> - Version bumps in package.json files (patch versions)
> - CHANGELOG.md updates documenting dependency updates
> - Deleted changeset markdown files consumed by release process
>
> <sup>Risk assessment for [commit
00d9965](https://github.com/vercel/vercel/commit/00d9965d12c097c2375af4e717f17594ca2ed06c).</sup>
<!-- VADE_RISK_END -->

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Based on #14703

This updates only `allowQuery` for fallback HTML when the route is a
true `partialFallback` (PPR fallback with postponed state) and cache
components is enabled. For all other fallback cases, behavior stays the
same as today (allowQuery is cleared to [] for shared fallback caching).

This change is needed because partial-fallback shells can be
param-specific, so collapsing them to one shared fallback cache key can
serve the wrong shell across params and block correct upgrade behavior.
Gating this behind `partialFallback` lets us roll out the new behavior
safely and independently, without changing legacy fallback semantics for
non-partial paths.

<!-- VADE_RISK_START -->
> [!NOTE]
> Low Risk Change
>
> This PR modifies caching behavior for partial fallback shells by
conditionally varying the allowQuery parameter, which is a Next.js
build/rendering optimization change rather than a security or data
schema change.
> 
> - Adds conditional logic for `htmlAllowQuery` based on
`partialFallback` and `isAppClientParamParsingEnabled`
> - Moves `partialFallback` variable declaration earlier in function
> - Updates comments explaining fallback caching behavior
>
> <sup>Risk assessment for [commit
0fc83c1](https://github.com/vercel/vercel/commit/0fc83c1231498eecad58db950cd0bfcb166004e4).</sup>
<!-- VADE_RISK_END -->

Based on #14703

This updates only `allowQuery` for fallback HTML when the route is a
true `partialFallback` (PPR fallback with postponed state) and cache
components is enabled. For all other fallback cases, behavior stays the
same as today (allowQuery is cleared to [] for shared fallback caching).

This change is needed because partial-fallback shells can be
param-specific, so collapsing them to one shared fallback cache key can
serve the wrong shell across params and block correct upgrade behavior.
Gating this behind `partialFallback` lets us roll out the new behavior
safely and independently, without changing legacy fallback semantics for
non-partial paths.

<!-- VADE_RISK_START -->
> [!NOTE]
> Low Risk Change
>
> This PR modifies caching behavior for partial fallback shells by
conditionally varying the allowQuery parameter, which is a Next.js
build/rendering optimization change rather than a security or data
schema change.
> 
> - Adds conditional logic for `htmlAllowQuery` based on
`partialFallback` and `isAppClientParamParsingEnabled`
> - Moves `partialFallback` variable declaration earlier in function
> - Updates comments explaining fallback caching behavior
>
> <sup>Risk assessment for [commit
0fc83c1](https://github.com/vercel/vercel/commit/0fc83c1231498eecad58db950cd0bfcb166004e4).</sup>
<!-- VADE_RISK_END -->

In #69282, we landed support for
Partial Fallback Prerendering. The intention behind this feature was to
be able to upgrade from a partial fallback (essentially the UI produced
when `await params` is dynamic, ie the param was not part of
`generateStaticParams` at build time) to a route shell (when the param
values are filled in, and thus we can prerender more of the page).

It was reverted in #79258 because
we didn't add first-class support to this in the build output API and
the necessary infrastructure changes to perform similar behavior that
this PR does to trigger a background revalidation with params filled in.

This re-lands the feature in Next.js now that upstream support landed
(vercel/vercel#14703,
vercel/vercel#15338, and Vercel infra changes
which are rolling out)

In #69282, we landed support for
Partial Fallback Prerendering. The intention behind this feature was to
be able to upgrade from a partial fallback (essentially the UI produced
when `await params` is dynamic, ie the param was not part of
`generateStaticParams` at build time) to a route shell (when the param
values are filled in, and thus we can prerender more of the page).

It was reverted in #79258 because
we didn't add first-class support to this in the build output API and
the necessary infrastructure changes to perform similar behavior that
this PR does to trigger a background revalidation with params filled in.

This re-lands the feature in Next.js now that upstream support landed
(vercel/vercel#14703,
vercel/vercel#15338, and Vercel infra changes
which are rolling out)