Dango 1.0.13

Dango 1.0.13

A patch release. The headline fix: new projects' Metabase page (/metabase, the Dashboards tab) was blank in modern browsers — fixed. It also makes CI/scripted setup (dango init --skip-wizard) finish with a working Metabase, makes dango dashboard provision work without asking for a password, fixes custom Metabase ports end to end, and hardens the cloud commands (credential-loss detection, remote sync failure reporting, backup restore, shell quoting).

Upgrade notes

• pip install -U getdango (or re-run the installer). Existing projects keep their Metabase version; the /metabase fix is in Dango itself, so it applies to every project, including projects created with 1.0.8–1.0.12 (Metabase v0.62.18), which are the ones that showed the blank page. Projects created before 1.0.8 (Metabase v0.59.1) were never affected.
• Changed default: dango init --skip-wizard without DANGO_ADMIN_EMAIL now creates admin@dango.test (was admin@localhost, which Metabase rejects). To use a real address: dango auth add-user you@yourcompany.com --role admin --password, sign in once as that user, then dango auth delete-user admin@dango.test. (After the delete the Metabase admin identity remains the placeholder admin@dango.test; nothing breaks.)
• A project that still has the old admin@localhost admin: dango start now says Metabase was not set up and prints the fix: dango auth add-user <dotted email> --role admin --password, then DANGO_ADMIN_EMAIL=<that email> dango start.

Known limitations (honest list)

• Cloud changes (lost-credential detection and dango remote metabase-repair-admin, remote sync start reporting, reset-metabase, backup/rollback quoting, push port and login-timeout handling, remote logs --service metabase) were exercised on a live DigitalOcean server on 2026-10-07. Not exercised live, automated tests only: Spaces backup download/restore, the scheduled-backup timer, and the single Metabase image build on first deploy.
• dango serve reports a rejected Metabase credential only after Metabase becomes healthy (up to 3 minutes after start); a project whose Metabase never becomes healthy prints nothing.
• The background remote sync launch was checked on a server whose login shell is bash; other non-POSIX login shells are untested.
• dango remote push removes dbt models that exist only on the server (for example staging models a server-side sync generated); the next dango remote sync regenerates them.
• On a fresh server the dbt-docs container shows unhealthy until docs are first generated (by the first sync).
• docs for Python versions on the installation page said 3.10–3.12; Dango supports 3.10–3.13.
• The demo video's footer says Dango v1.0.12.

See the changelog for the full list.