Skip to content

[pull] canary from vercel:canary#146

Merged
pull[bot] merged 4 commits into
code:canaryfrom
vercel:canary
May 21, 2025
Merged

[pull] canary from vercel:canary#146
pull[bot] merged 4 commits into
code:canaryfrom
vercel:canary

Conversation

@pull

@pull pull Bot commented May 21, 2025

Copy link
Copy Markdown

See Commits and Changes for more details.


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

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

timneutkens and others added 4 commits May 20, 2025 21:31
## What?

Turbopack doesn't fail in this case as it can process server-side assets
regardless of if they're also in the client layer. That's something we
couldn't do with webpack.
This allows us to run the E2E deploy tests against a custom tarball or
version without triggering a canary release.
Continuation of #78166 this
implements the `handler` interface for pages routes, This does not move
the response handling inside of the handler yet as that will be in a
follow-up PR to keep the changes isolated. This still returns the
`RenderResult` for the `base-server` to continue to handle.

Validated against `vercel/vercel` deploy tests here
vercel/vercel#13349
@pull pull Bot added the ⤵️ pull label May 21, 2025
@pull pull Bot merged commit d937203 into code:canary May 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants