Repository navigation
Pin better-auth to the exact release CI tested - #56
Merged
Merged
Conversation
@pgstencil/auth reads Better Auth internals, and a patch release can change them: 1.7.7 renamed its OAuth state rows, which broke OAuth for any 0.2.x install that resolved it through `~1.7.3`. An exact pin means an application only ever runs the Better Auth release pgstencil tested; each upgrade reaches applications through a pgstencil release. Better Auth pins its own @better-auth/* packages and better-call exactly, so this freezes the whole stack. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
@pgstencil/authreads Better Auth internals, such as itsverificationrows for OAuth state. The~1.7.xrange let a consumer resolve a Better Auth patch our CI never ran against. That already broke OAuth: published@pgstencil/auth@0.2.1declares~1.7.3, so a fresh install picks up 1.7.7, which renamed its OAuth state rows (fixed in #50).packages/auth/package.jsonchanges from~1.7.7to1.7.7. Better Auth pins its own@better-auth/*packages andbetter-callexactly, so this freezes the whole stack we test.rangeStrategy: "bump"rule forpackages/*dependencies keeps updating an exact version.Trade-off: a Better Auth fix, including a security fix, now reaches applications only through a pgstencil release. Renovate's vulnerability alerts already skip the weekly schedule, and an app can use a pnpm override in an emergency.
No version bump. This ships with the next release.
Test plan
pnpm format:check,pnpm typecheckpnpm packages:verify: the installed consumer's@pgstencil/authdeclaresbetter-auth: 1.7.7🤖 Generated with Claude Code