[next] Apply routes-manifest onMatchHeaders#14903
Merged
Conversation
🦋 Changeset detectedLatest commit: 9bd37d6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
📦 CLI Tarball ReadyThe Vercel CLI tarball for this PR is now available! Quick TestYou can test this PR's CLI directly by running: npx https://vercel-dhh8eo64d.vercel.sh/tarballs/vercel.tgz --helpUse in vercel.jsonTo use this CLI version in your project builds, add to your {
"build": {
"env": {
"VERCEL_CLI_VERSION": "vercel@https://vercel-dhh8eo64d.vercel.sh/tarballs/vercel.tgz"
}
}
} |
Contributor
🧪 Unit Test StrategyComparing: Strategy: Affected packages only ✅ Only testing packages that have been modified or depend on modified packages. Affected packages - 2 (5%)
Unaffected packages - 38 (95%)
Results
This comment is automatically generated based on the affected testing strategy |
ijjk
approved these changes
Feb 6, 2026
This reverts commit 461f968.
Merged
ijjk
pushed a commit
that referenced
this pull request
Feb 6, 2026
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@50.13.0 ### Minor Changes - Adds experimental support for embedding Vercel Flags definitions during build. ([#14838](#14838)) When `VERCEL_EXPERIMENTAL_EMBED_FLAG_DEFINITIONS=1` is set, the CLI scans environment variables for Vercel Flags SDK keys (prefixed with `vf_`) and fetches their flag definitions. The definitions are written to a synthetic `@vercel/flags-definitions` module in `node_modules` that can be imported at runtime. ### Patch Changes - Updated dependencies \[[`a172b3c68ba75bf8f9e517fe476cebe2e32bdb8c`](a172b3c), [`d59e76b47c3a491afe5dff6ee76224ed77ac8d74`](d59e76b)]: - @vercel/next@4.15.25 ## @vercel/next@4.15.25 ### Patch Changes - [next] Apply routes-manifest onMatchHeaders ([#14903](#14903)) - Make adapters flag explicit value for opt-in ([#14905](#14905)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
mischnic
added a commit
to vercel/next.js
that referenced
this pull request
Feb 6, 2026
When proxying through multiple projects, this header would get overwritten by the proxy project: - the header would be the proxy's deployment id - `process.env.NEXT_DEPLOYMENT_ID` would be the origin's deployment id Needs vercel/vercel#14903
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Corresponds to vercel/next.js#89593