Skip to content

logfire-0.15.3

Latest

Choose a tag to compare

@github-actions github-actions released this 12 Nov 13:27
ba4706f

Summary

Chart 0.15.3, on platform v2026-11-11.03. It promotes 0.15.3-rc.1 to stable without changes.

  • Sign-in settings now have their own auth values:

    auth:
      passwordLogin: true            # email and password sign-in
      passkeys: true                 # fingerprint, face unlock, or security key
      sessionMaxLifetime: PT8H       # longest browser session, ISO 8601; empty for no limit
      passwordlessEmailSignup: false # account creation without a password; needs smtp.* or MailDev

    sessionMaxLifetime is new in this release. A new session ends after this time, or sooner if the user's own session setting is shorter. Sessions that already exist keep their expiration. Without SCIM, a group-mapping change reaches a user only when they sign in again through the identity provider, so this limit also caps how long that takes.

  • auth.passwordLogin: false now removes email and password sign-in from the Logfire sign-in page, and also turns off Dex's password database. Before this release, logfire-dex.config.enablePasswordDB: false turned off only Dex's own login form, and the Logfire page still offered email and password sign-in. That value still works.

  • Sign-in with a code sent by email is separate from auth.passwordLogin. It stays available while email delivery is configured.

  • If an adminApiKeys entry points to a key that was revoked or that expired, the backend now starts. It logs a warning that names the key, and the key stays revoked. With 0.15.2, the backend failed to start in that case and restarted in a loop.

Upgrade notes

You do not need to change your values.

  • If you set logfire-dex.config.enablePasswordDB: false, users no longer see the email and password option after the upgrade. That was the intent of the value. Users who signed in with a password must sign in through a Dex connector. You can replace the value with auth.passwordLogin: false.
  • With auth.passwordLogin: false, Dex does not start without a connector under logfire-dex.config.connectors. This is the same requirement as enablePasswordDB: false in earlier versions.
  • If you set PASSKEYS_ENABLED or SESSION_MAX_LIFETIME in logfire-backend.env, that value still applies and takes precedence over auth. You can move it to auth.
  • If you mirror images to a private registry, mirror the images for appVersion 6dc21200. The image names are the same as in 0.15.2.
  • The migration Job adds tables and columns to the crud database during the upgrade.
  • You can roll back to 0.15.2. Its images work with the new schema. You still cannot downgrade to 0.14.x.

Breaking changes

None.

PR: #365


Helm chart for self-hosted Pydantic Logfire