chore(deps): upgrade better-auth to 1.7.3 - #93
Merged
Conversation
The previous sweep held better-auth at 1.6.x with a tilde range because 1.7.0-1.7.2 rekey accounts on (issuer, accountId) and require a backfill, and 1.7.3 - which reverts that and restores the 1.6 core account schema - had not yet cleared pnpm's 24h release-age gate. It has now, and it is the latest dist-tag. Confirmed no migration is needed rather than taking the release note at face value: diffing @better-auth/core 1.6.30 against 1.7.3 shows the auth table column definitions are identical. The only schema-side change is additive index metadata consumed by better-auth's own migration generator, which neither app calls - flnk and wepush manage their schema with drizzle-kit. None of the other 1.7.0 breaking surfaces are in use either: no experimental joins, no OAuth validAudiences, no MCP or SCIM plugin and no two-factor. Verified: flnk and wepush typecheck and build clean, flnk's 47 tests pass, and biome stays clean at 1182 files. The lockfile change is scoped to better-auth alone.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Why now
The previous sweep (#92) deliberately held better-auth at 1.6.x with a
~1.6.29range. 1.7.0–1.7.2 rekey accounts on(issuer, accountId)and require a disruptive account backfill; 1.7.3 reverts that and restores the 1.6 core account schema, but at the time it had only just been published and was still inside pnpm's 24hminimumReleaseAgegate.1.7.3 is now ~30h old and is
dist-tags.latest, so the hold can be lifted straight to^1.7.3, skipping the 1.7.0–1.7.2 window entirely.No migration needed — verified, not assumed
Rather than taking the release note at face value, I diffed the authoritative table definitions (
@better-auth/core/dist/db/get-tables.mjs) between 1.6.30 and 1.7.3:user/session/account/verificationare identical.indexesmetadata, plus a newgetAuthTablesWithResolvedIndexeshelper. That metadata feeds better-auth's owngetMigrations, which neither app calls — flnk and wepush manage their schema with drizzle-kit (db:gen/db:migrate).So there is nothing to generate and nothing to apply before deploying.
Other 1.7.0 breaking surfaces — none in use
experimental: { joins: true }→advanced.database.joins@better-auth/mcpvalidAudiences→resourcesenableTwoFactordiscriminatedmethodBoth apps use only
drizzleAdapter,nextCookies,socialProviders(Google/GitHub) andaccount.accountLinking.Verification
apps/flnkandapps/wepush— typecheck clean, coldnext buildgreenbiome check .— clean at 1182 files, unchangedNote
better-authdeclares avitest ^2||^3||^4peer and the workspace is on vitest 5, sopnpm peers checkreports one unmet peer. It is benign — better-auth only uses vitest for its own test suite.