Release 1.1.1 · PT-Perkasa-Pilar-Utama/testate

One fix, released 9 September 2026, for pointing a Testate container at a Supabase database. The full record is in the CHANGELOG.

Fixed

An IPv6-only cloud host names the IPv4 way out. The direct Supabase host, db.<ref>.supabase.co, has only an IPv6 address. Docker Desktop's resolver drops it on a machine without IPv6, so the probe said the name does not resolve and pointed at container names and host.docker.internal, neither of which applies. A dotted name that fails to resolve inside a container now leads with the IPv6-only cause and the provider's IPv4 endpoint: on Supabase, the Session pooler on port 5432 with user postgres.<ref>.
A missing IPv6 route is an unreachable host, not a failed batch. Where the resolver does return the address, Linux Docker fails the connect with ENETUNREACH. Postgres and MySQL now report that as unreachable, like a refused connection.
The connecting guide had Supabase backwards. It said to use the direct host and avoid the pooler. Section C now gives the Session pooler values and keeps the transaction pooler on 6543 as the one to avoid.

docker pull ghcr.io/pt-perkasa-pilar-utama/testate:1.1.1

No migration, no new setting. Compare v1.1.0...v1.1.1.