feat(next-auth): add Vercel skew protection headers to client fetches#13405
Open
brookemosby wants to merge 1 commit intonextauthjs:mainfrom
Open
feat(next-auth): add Vercel skew protection headers to client fetches#13405brookemosby wants to merge 1 commit intonextauthjs:mainfrom
brookemosby wants to merge 1 commit intonextauthjs:mainfrom
Conversation
Attach x-deployment-id to SessionProvider and client auth requests so plain fetch calls stay pinned during rolling releases. Respects VERCEL_SKEW_PROTECTION_ENABLED and resolves deployment id from Next/Vercel conventions. Made-with: Cursor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
@brookemosby is attempting to deploy a commit to the authjs Team on Vercel. A member of the Team first needs to authorize it. |
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
1 participant
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.
Attach x-deployment-id to SessionProvider and client auth requests so plain fetch calls stay pinned during rolling releases. Respects VERCEL_SKEW_PROTECTION_ENABLED and resolves deployment id from Next/Vercel conventions.
Made-with: Cursor
☕️ Reasoning
🧢 Checklist
🎫 Affected issues
📌 Resources