Skip to content

supabase-dashboard 0.3.0-dev.4

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Nov 12:01
· 22 commits to main since this release

What's new

Invitation emails. With a mail server configured, the dashboard emails the invitation link to the invited address once the invitation is saved. The page still shows the link once and says whether the email went out. If the send fails, the invitation still works and you can send the link by hand; the dashboard doesn't retry. Each send is in the audit log as organization.invitation_email, without the message or the link. Mail is off unless SUPABASE_DASHBOARD_SMTP_URL is set. The connection always uses TLS (smtps://, or smtp:// with STARTTLS required), and the password is read from a file or a variable, never from the URL. See "Invitation email" in docs/deployment.md.

Integrations tab. The list of Dokploy environments on an organization's Integrations tab was indented without bullets and its two buttons didn't line up, because it shared a style with the admin page. It has its own styles now.

Dokploy install guide. The guide explains the bind source path does not exist: .../files/secret.key error: the secret.key file mount is missing, or its File Path isn't exactly secret.key.

Upgrading from 0.3.0-dev.3

  1. Back up the metadata database.
  2. Set SUPABASE_DASHBOARD_VERSION=0.3.0-dev.4, then docker compose pull && docker compose up -d. This release has no migration.
  3. To turn on invitation emails, add the SUPABASE_DASHBOARD_SMTP_* and SUPABASE_DASHBOARD_MAIL_FROM settings from .env.example, and the smtp_password secret, to your files. They're new in this release's .env.example and compose.yaml.

Known limitations

  • Password reset by email isn't implemented. Reset a forgotten password with supabase-dashboard-server reset-password on the server.
  • There's no Resend adapter and no way to resend an open invitation's email.
  • Mail settings on Dokploy are documented but haven't been tried there. They were tested with the server against Mailpit.

Container image (linux/amd64, linux/arm64):

docker pull ghcr.io/filipnone/supabase-dashboard:0.3.0-dev.4

To deploy on a Linux server with Docker, download supabase-dashboard-0.3.0-dev.4-docker.tar.gz, unpack it, and follow its README. Nothing is compiled on the server.

The *-linux-gnu.tar.gz files contain the same server binary and web assets for running without Docker (glibc 2.36 or newer).

This is a development pre-release. Expect breaking changes between dev releases. Database migrations only move forward: back up the metadata database before upgrading, and do not downgrade.

Full Changelog: v0.3.0-dev.3...v0.3.0-dev.4