[pull] canary from vercel:canary#799
Merged
pull[bot] merged 15 commits intocode:canaryfrom Feb 18, 2026
Merged
Conversation
Fork the set of deployment tests so they run with both turbopack and webpack. Now that turbopack is the default bundler we need this coverage. Because we are now running twice as many tests, decrease concurrency, otherwise we hit rate limits on vercel. There were attempts to improve rate limit recovery in the vercel CLI (vercel/vercel#14443 and vercel/vercel#14407) which helped but did not solve the issue. Also there was an investigation into the API service where we discovered some suspicious but ultimately correct code (vercel/api#55967). The basic issue is that the vercel CLI polls `api-deployments-get` fairly aggressively at the beginning of a deploymnet, and since we start so many deployments in parallel we will always hit the rate limits. The recovery logic in the CLI is good but has (reasonably) a fixed set of retries it will attempt, inevitably some tasks get unlucky. So retrying the test does work, but really we should slow down which is what we do here. 😥 https://github.com/vercel/next.js/actions/runs/20290161194/job/58272593085 Fixes PACK-5613 --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
This avoids cancelling on canary branch when a commit is merged while previous commit is still running ## Summary - keep cancel-in-progress behavior for pull_request runs - stop canceling in-progress runs for follow-up pushes to canary by using a per-run concurrency group for push events x-ref: https://github.com/vercel/next.js/actions/runs/22113161316/job/63914496141
## Summary
Prefetch hints were previously stored in CacheNodeSeedData — the payload
the server sends for each segment's React content. This moves them to
FlightRouterState, the route tree structure that the server sends
alongside the seed data. FlightRouterState is a better home because
prefetch hints describe properties of the route structure (loading
boundaries, instant configs) rather than properties of the rendered
content. It also ensures that hints are always available during
navigations, not just prefetches.
Since this changes the FlightRouterState tuple layout anyway, it also
folds the existing `isRootLayout` boolean and `HasLoadingBoundary` enum
into the same bitmask field at FlightRouterState[4].
## Test plan
- Existing unit tests updated for new format
(`flight-data-helpers.test.ts`, `types.test.ts`)
- MPA navigation test validates root layout change detection via bitmask
- `prefetch-true-instant` e2e test validates Link `prefetch={true}`
behavior with instant routes
…90056) The recent change to move task description formatting onto `TaskGuard` introduced a subtle issue when formatting these rare error messages.
Stacked on #90065 The older methods were so close in function to runInSequentialTasks we've now unified the interface and use it consistently everywhere.
…e" (#90098) Reverts #90096 * always `track_mutation()` before the mutation * only `track_mutation()` if we are actually going to mutate The previous attempt was reverted because we would call `track_modification` too often which lead to a test failure in the filesystem-cache-test because the DB grew too much.
Stacked on #89978 When the AbortSignal passed to the StagedRenderingController is aborted there is some logic to potentially abort any unresolved stage promises. Semantically anything we have a render with a stage controller that is aborted we must ensure no stage promises are left in a perpetually pending state.
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
9 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 : )