Version Packages

[github-actions]

This PR was opened by the Changesets release 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.4.1

Patch Changes

• Updated dependencies [f0d7d32]
  • @vercel/build-utils@13.22.1

@vercel/build-utils@13.22.1

Patch Changes

• f0d7d32: Disable response streaming for lambdas with awsLambdaHandler set inside getLambdaSupportsStreaming. This closes a gap where non-Node builders (e.g. @vercel/redwood) constructed NodejsLambda with awsLambdaHandler but no explicit supportsResponseStreaming, causing finalizeLambda to silently flip streaming on for AWS custom handlers. With the gate now enforced centrally in finalizeLambda, the equivalent @vercel/node build-time check from [node] Disable response streaming for AWS custom handler lambdas #16266 is consolidated away — all builders go through the same gate.

@vercel/cervel@0.1.2

Patch Changes

• @vercel/backends@0.4.1

vercel@53.3.2

Patch Changes

• Updated dependencies [f0d7d32]
  • @vercel/build-utils@13.22.1
  • @vercel/node@5.7.17
  • @vercel/backends@0.4.1
  • @vercel/elysia@0.1.75
  • @vercel/express@0.1.85
  • @vercel/fastify@0.1.78
  • @vercel/go@3.6.0
  • @vercel/h3@0.1.84
  • @vercel/hono@0.2.78
  • @vercel/hydrogen@1.3.7
  • @vercel/koa@0.1.58
  • @vercel/nestjs@0.2.79
  • @vercel/next@4.17.1
  • @vercel/python@6.39.0
  • @vercel/redwood@2.4.13
  • @vercel/remix-builder@5.8.1
  • @vercel/ruby@2.3.2
  • @vercel/rust@1.2.0
  • @vercel/static-build@2.9.24

@vercel/client@17.4.2

Patch Changes

• Updated dependencies [f0d7d32]
  • @vercel/build-utils@13.22.1

@vercel/elysia@0.1.75

Patch Changes

• Updated dependencies [f0d7d32]
  • @vercel/node@5.7.17

@vercel/express@0.1.85

Patch Changes

• Updated dependencies [f0d7d32]
  • @vercel/node@5.7.17
  • @vercel/cervel@0.1.2

@vercel/fastify@0.1.78

Patch Changes

• Updated dependencies [f0d7d32]
  • @vercel/node@5.7.17

@vercel/fs-detectors@6.2.1

Patch Changes

• Updated dependencies [f0d7d32]
  • @vercel/build-utils@13.22.1

@vercel/gatsby-plugin-vercel-builder@2.2.2

Patch Changes

• Updated dependencies [f0d7d32]
  • @vercel/build-utils@13.22.1

@vercel/h3@0.1.84

Patch Changes

• Updated dependencies [f0d7d32]
  • @vercel/node@5.7.17

@vercel/hono@0.2.78

Patch Changes

• Updated dependencies [f0d7d32]
  • @vercel/node@5.7.17

@vercel/koa@0.1.58

Patch Changes

• Updated dependencies [f0d7d32]
  • @vercel/node@5.7.17

@vercel/nestjs@0.2.79

Patch Changes

• Updated dependencies [f0d7d32]
  • @vercel/node@5.7.17

@vercel/node@5.7.17

Patch Changes

• f0d7d32: Disable response streaming for lambdas with awsLambdaHandler set inside getLambdaSupportsStreaming. This closes a gap where non-Node builders (e.g. @vercel/redwood) constructed NodejsLambda with awsLambdaHandler but no explicit supportsResponseStreaming, causing finalizeLambda to silently flip streaming on for AWS custom handlers. With the gate now enforced centrally in finalizeLambda, the equivalent @vercel/node build-time check from [node] Disable response streaming for AWS custom handler lambdas #16266 is consolidated away — all builders go through the same gate.
• Updated dependencies [f0d7d32]
  • @vercel/build-utils@13.22.1

@vercel/static-build@2.9.24

Patch Changes

• @vercel/gatsby-plugin-vercel-builder@2.2.2

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
vercel	Ready	Preview, Comment	May 10, 2026 4:06pm

[vercel]

Low Risk — automated changeset release — version bumps + changelog updates only

• packages/*/package.json: version number increments
• packages/*/CHANGELOG.md: release notes added
• .changeset/*.md: consumed changeset files deleted

^{Assessed at f2ed288.}