[pull] canary from vercel:canary #746
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…89171) With Cache Components enabled in development, fetches without an explicit cache config were incorrectly routed through `createCachedPrerenderResponse` during the cache filling phase due to the `serverComponentsHmrCache` condition. This function awaits the entire response before returning to the caller, which prevents infinitely streaming responses from ever being read or aborted. This is a regression that was introduced in #84088. These fetches should be treated as dynamic and use `createCachedDynamicResponse` instead, which returns immediately and caches in the background with proper error handling. The fix adds `isCacheableRevalidate` to the condition so only explicitly cacheable fetches use the blocking path. Additionally, the "Failed to set fetch cache" warning is now suppressed when the request's abort signal was triggered, since aborting is intentional.
This should really be an error, but let's start with making it a warning the only missing piece will be somehow showing the line/col information of the offending reference, this is currently very hard to figure out <img width="1265" height="428" alt="Bildschirmfoto 2026-01-28 um 12 32 17" src="https://github.com/user-attachments/assets/80e48fa8-a021-4ca2-a966-26164c42b1dd" />
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
…89163) Co-authored-by: Cursor Agent <cursoragent@cursor.com>
This updates to run the entire E2E deploy tests same as we do currently but with adapters enabled to catch regressions there. These run on a separate test team to isolate from existing test team and avoid rate limits. Test run of the workflow done here https://github.com/vercel/next.js/actions/runs/21418745794
Not a hard requirement so removing in [response to request](#88958 (comment))
This auto-generated PR updates the production integration test manifest used when testing Rspack.
This applies fixes/regression tests for reported issues in nextjs/adapters-wg#1
This aims to remove assertions that were specific to Vercel so that other platforms can re-use our E2E deploy workflow.
## Summary Adds support for custom deploy scripts in the `next-deploy` test mode via two new environment variables: - `NEXT_TEST_DEPLOY_SCRIPT_PATH` - Path to a custom script that deploys the project and outputs the deployment URL to stdout - `NEXT_TEST_DEPLOY_LOGS_SCRIPT_PATH` - Path to a custom script that fetches build logs (required when using custom deploy script) This allows running deploy tests against non-Vercel deployment targets. ### Priority Order 1. `NEXT_TEST_DEPLOY_URL` - If set, uses existing deployment (no deploy happens) 2. `NEXT_TEST_DEPLOY_SCRIPT_PATH` - If set, uses custom deploy script 3. Default Vercel CLI logic - If neither is set ### Script Interface **Deploy script** receives: - `NEXT_TEST_DIR` - The test directory containing the Next.js project - All test-specific environment variables - Must output deployment URL to stdout **Logs script** receives: - `NEXT_TEST_DIR` - The test directory - `NEXT_TEST_DEPLOY_URL` - The deployment URL - Must output build logs containing `BUILD_ID: <id>` pattern Verified existing flow is still working in: https://github.com/vercel/next.js/actions/runs/21465304133
### What? Adds GPTBot to matcher for returning true if it is a known bot. An example UserAgent string for this type of bot is "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; GPTBot/1.3; +https://openai.com/gptbot)" ### Why? This is a known bot and so it should be treated as such ### How? Self explanatory Co-authored-by: davidgolden <david@soprisapps.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
8 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 : )