From 4963e355f16257dab0a1de4fb3c048f090defac5 Mon Sep 17 00:00:00 2001 From: DJ Mountney Date: Wed, 21 Oct 2026 18:03:49 -0700 Subject: [PATCH] fix: update the images to 2026-10-14-002 so accounts created before 1.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 --- charts/currents/Chart.yaml | 2 +- charts/currents/values.yaml | 2 +- docs/configuration.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/charts/currents/Chart.yaml b/charts/currents/Chart.yaml index a37aefa..6de2354 100644 --- a/charts/currents/Chart.yaml +++ b/charts/currents/Chart.yaml @@ -8,7 +8,7 @@ type: application version: 1.0.0 # Version number of the application being deployed. # Versions are not expected to follow Semantic Versioning. They should reflect the version the application is using. -appVersion: "2026-10-14-001" +appVersion: "2026-10-14-002" maintainers: - name: Currents-dev url: https://currents.dev diff --git a/charts/currents/values.yaml b/charts/currents/values.yaml index dcce416..15b23f6 100644 --- a/charts/currents/values.yaml +++ b/charts/currents/values.yaml @@ -27,7 +27,7 @@ currents: # @section -- Frequently Used key: password # -- The image tag to use for the Currents images - imageTag: 2026-10-14-001 + imageTag: 2026-10-14-002 email: # -- Which transport to send outgoing email through: `smtp` or `ses`. # With `ses` the SMTP settings are ignored and no SMTP credentials are diff --git a/docs/configuration.md b/docs/configuration.md index bdeeda6..d58b34c 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -1,6 +1,6 @@ # Configuration Reference -![Version: 1.0.0](https://img.shields.io/badge/Version-1.0.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 2026-10-14-001](https://img.shields.io/badge/AppVersion-2026--10--14--001-informational?style=flat-square) +![Version: 1.0.0](https://img.shields.io/badge/Version-1.0.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 2026-10-14-002](https://img.shields.io/badge/AppVersion-2026--10--14--002-informational?style=flat-square) ## Requirements @@ -112,7 +112,7 @@ The following table lists the configurable parameters of the `currents` chart an | Key | Type | Default | Description | |-----|------|---------|-------------| | currents.rootUser.email | string | `"admin@{{ .Values.currents.domains.appHost }}"` | The email address of the root user | -| currents.imageTag | string | `"2026-10-14-001"` | The image tag to use for the Currents images | +| currents.imageTag | string | `"2026-10-14-002"` | The image tag to use for the Currents images | | currents.email.transporter | string | `"smtp"` | Which transport to send outgoing email through: `smtp` or `ses`. With `ses` the SMTP settings are ignored and no SMTP credentials are needed — the AWS SDK resolves credentials from the pod itself, so grant the Currents service account permission to send. See [Using IAM Roles for Sending Email with SES](./eks/iam.md#using-iam-roles-for-sending-email-with-ses). | | currents.email.from | tpl/string | `""` | The email address to send from. Defaults to `currents.email.smtp.from` when unset, which is retained for compatibility. | | currents.email.ses.region | string | `""` | The AWS region to send through. Required when `transporter` is `ses`, and the `from` address must be a verified identity in that region. |