Repository navigation
fix(auth): upgrade Better Auth and preserve issuer-scoped identities - #466
Merged
Merged
Conversation
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.
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.
Upgrade Better Auth, its API-key and passkey plugins from 1.7.1 to 1.7.14, and align JOSE at 6.2.13 across its consumers.
Better Auth no longer writes the required account issuer column introduced in 1.7.1. Migration 0069 removes that constraint and encodes each OAuth issuer and subject together, preserving identity separation when an administrator changes or recreates a provider. Password credentials, account ownership, tokens, and sessions are preserved. Ambiguous account keys stop migration before writes; downgrading requires a pre-upgrade backup.
Update direct account writes, backup migration compatibility, fixtures, security documentation, and the release changeset.
CI also detected newly reviewed GHSA-gcqx-w48m-w2h4 in Expo's existing deepmerge 4.3.1 dependency. No fixed release is published. Patch source and both distributed bundles to reject proto in both copy loops. The Node regression against Expo's resolved dependency fails without the patch and passes with it, including normal merge compatibility. Record the patch-backed audit exception until an upstream fixed release is available. Regression coverage checks migrated OAuth ownership, synthetic issuers, duplicate keys, and issuer replacement; removing issuer separation makes the new sign-in regression fail.
Validation: