Repository navigation
fix: update the images to 2026-10-14-002 so accounts created before 1.0.0 sign in again [ENG-1851] - #66
Merged
Conversation
….0.0 sign in again [ENG-1851] The 2026-10-14-001 images run Better Auth 1.7.1, which looks an account up by an `issuer` field that accounts created on chart 0.8.x do not have. After the upgrade every existing user was refused: SAML sign-ins redirected with `account_not_linked`, and the root admin's password sign-in answered `INVALID_EMAIL_OR_PASSWORD`. 2026-10-14-002 is 2026-10-14-001 plus currents-dev/currents#4480, which moves to Better Auth 1.7.12. It looks accounts up by provider again, so those users sign in with no change to the database. The scheduler's startup migration drops the `(issuer, accountId)` unique index 1.7.1 created on the first new account. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Baz, why does this need human review? |
|
This is a release metadata change that selects the deployed Currents image, so human review confirms |
maxigimenez
approved these changes
Oct 23, 2026
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
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.
Owner: @twk3
Linear: ENG-1851
Moves the chart to the
2026-10-14-002images, which fix existing users being locked out after upgrading to chart1.0.0.Why
The
2026-10-14-001images run Better Auth 1.7.1. It looks an account up by anissuerfield that accounts created on chart0.8.xdo not have, so after the upgrade every existing user was refused:account_not_linked.INVALID_EMAIL_OR_PASSWORD.2026-10-14-002runs Better Auth 1.7.12, which finds those accounts again with no change to the database. The scheduler's startup migration drops the(issuer, accountId)index 1.7.1 created on the first new account.Changes
currents.imageTagandappVersionmove to2026-10-14-002.docs/configuration.mdis regenerated withscripts/build-docs.sh; only the two version lines changed.Testing
helm lintpasses, andhelm templaterenders2026-10-14-002for all six services.0.8.1, upgraded to1.0.0and then to locally built images of #4480. The lockout reproduced on1.0.0and cleared on the patch, on both upgrade paths: through1.0.0, and straight from0.8.1. Details and recordings are on currents-dev/currents#4480.Follow-up
A separate
release: 1.0.1PR bumps the chart version and the changelog, as0.8.1did. It also updatesdocs/eks/upgrade-1.0.md, which pins--version 1.0.0and names the2026-10-14-001images, and adds a section for installs already on2026-10-14-001.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.