Skip to content

fix: update the images to 2026-10-14-002 so accounts created before 1.0.0 sign in again [ENG-1851] - #66

Merged
twk3 merged 1 commit into
mainfrom
fix/eng-1851-images-2026-10-14-002
Oct 23, 2026
Merged

twk3 merged 1 commit into
mainfrom
fix/eng-1851-images-2026-10-14-002

Conversation

@twk3

@twk3 twk3 commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Owner: @twk3
Linear: ENG-1851

Moves the chart to the 2026-10-14-002 images, which fix existing users being locked out after upgrading to chart 1.0.0.

Why

The 2026-10-14-001 images run Better Auth 1.7.1. It looks an account up by an issuer field that accounts created on chart 0.8.x do not have, so after the upgrade every existing user was refused:

  • SAML sign-ins returned to the sign-in page with account_not_linked.
  • The root admin's password sign-in answered INVALID_EMAIL_OR_PASSWORD.

2026-10-14-002 runs 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.imageTag and appVersion move to 2026-10-14-002.
  • docs/configuration.md is regenerated with scripts/build-docs.sh; only the two version lines changed.

Testing

  • helm lint passes, and helm template renders 2026-10-14-002 for all six services.
  • The fix was tested on a Docker Desktop install of chart 0.8.1, upgraded to 1.0.0 and then to locally built images of #4480. The lockout reproduced on 1.0.0 and cleared on the patch, on both upgrade paths: through 1.0.0, and straight from 0.8.1. Details and recordings are on currents-dev/currents#4480.

Follow-up

A separate release: 1.0.1 PR bumps the chart version and the changelog, as 0.8.1 did. It also updates docs/eks/upgrade-1.0.md, which pins --version 1.0.0 and names the 2026-10-14-001 images, and adds a section for installs already on 2026-10-14-001.

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

….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>
@baz-reviewer

baz-reviewer Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Review this PR on Baz

Baz Summary

Update the Helm chart and generated configuration reference to deploy the 2026-10-14-002 Currents images. Restore sign-in for pre-1.0 accounts by consuming the Better Auth fix and its startup migration, which removes the obsolete account index.

Latest Contributors(2)
UserCommitDate
dj@currents.devfix: update the images...October 22, 2026
agoldis@users.noreply....Refine namingApril 10, 2025


Merger  Activate to get a short verdict whether this PR is good to go or not

Skills  Activate Skill Maintainer to keep your skills up to date

Planner  This PR would have been improved with Baz Planner - Try it now

@twk3
twk3 marked this pull request as ready for review October 22, 2026 03:49
@twk3

twk3 commented Oct 22, 2026

Copy link
Copy Markdown
Contributor Author

Baz, why does this need human review?

@baz-reviewer

baz-reviewer Bot commented Oct 22, 2026

Copy link
Copy Markdown

This is a release metadata change that selects the deployed Currents image, so human review confirms 2026-10-14-002 is the intended, published tag and that the chart/docs remain consistent; the documentation is generated and checked automatically.

@twk3
twk3 merged commit f2fd600 into main Oct 23, 2026
3 checks passed
@twk3
twk3 deleted the fix/eng-1851-images-2026-10-14-002 branch October 23, 2026 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants