chore: upgrade @auth/nextjs
#76
Merged
Conversation
This file contains 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
|
@balazsorban44 is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
Closed
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
nextauthjs/next-auth@179c08d
Spent two hours on this.
The
x-forwarded-protoheader returnshttps, butURL#protocolreturnshttps:.This made our cookies not being properly set in secure (HTTPS) environments, causing various issues when deployed.
Fixes #28
You can run
pnpm up @auth/nextjsin your own project to apply this fix.