Repository navigation
Handle versioned i18n Pages API routing - #103
Draft
timneutkens wants to merge 1 commit into
Draft
timneutkens wants to merge 1 commit into
timneutkens wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: 878d37d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
Summary
Restore the i18n Pages API routing fix from #81 behind a versioned routing-manifest contract instead of a Next.js package-version check.
routing.version: 1as the legacy contract, preserving existing locale-prefixed API routing.routing.version: 2, keep/apiand nested Pages API paths canonical across wildcard-domain prefixing, default-locale prefixing,localeDetection: falsefallback routing, and locale-prefix removal. Similar prefixes such as/apiaryremain ordinary localized pages.This adapter change must be released and synced into the Vercel builder before Next.js starts emitting routing manifest v2. That rollout order decouples the two repositories' release schedules while preserving older Next.js behavior.
Paired Next.js change: vercel/next.js #97366.
Verification
pnpm --filter @next-community/adapter-vercel test --run(10 tests passed)pnpm --filter @next-community/adapter-vercel buildpnpm exec biome check packages/adapter/src/index.ts packages/adapter/src/routing.ts packages/adapter/src/routing.test.ts packages/adapter/package.json .changeset/fix-i18n-api-routes.md