Skip to content

v2026.10.6 — Automatic Better Auth schema migration

Choose a tag to compare

@tembo tembo released this 02 Oct 21:47
· 37 commits to main since this release
Immutable release. Only release title and notes can be modified.
a891b5a

Fixed

  • Better Auth schema mismatch during upgrades. Migration 0097 adds nullable alg and crv text columns to jwks, which the current JWT schema expects. It also removes NOT NULL constraints if those columns already exist. Existing signing keys and populated metadata are preserved. (#575)
  • Matching release defaults. Both compose image defaults select 2026.10.6 before tagging, so the tagged compose file and published images agree. (#576)

Upgrade order — no manual SQL required

  1. Deploy ghcr.io/tembo/tas-api:2026.10.6. The API automatically applies migration 0097 at startup. Confirm the migration completes and the API deployment becomes healthy.
  2. Then deploy ghcr.io/tembo/tas-web:2026.10.6.

For ECS, refresh the API service and wait for its new deployment to become healthy before refreshing web. The existing refresh workflow starts both deployments back-to-back; sequence them for this upgrade. If ECS rolls back, inspect the active task definition, image digest, service events, and API logs rather than relying only on the update-service command succeeding.

This addresses the confirmed jwks.alg / jwks.crv mismatch. If Better Auth reports other tables or columns, retain the complete schema report for diagnosis.

Validation

  • PostgreSQL 18 migration checks covered missing columns, pre-existing NOT NULL columns, repeat application, preservation of signing keys and existing metadata, and inserts omitting optional metadata.
  • Production web build and web/API CI passed.
  • Both versioned images are published, signed, and scanned before this GitHub release is published.

Full changelog: v2026.10.5...v2026.10.6