The aarch64 release lane needs a durable packaging correction without holding back the minor release.
A dependency pin protects the release date; a Nix correction protects repeatability across later builds.
Who you’d be doing this for
“Our security review is waiting on that image, and I’ve already had to move the maintenance window once.”
Bao Yusof · Backend Developer
Runs a self-hosted PostgreSQL deployment from Docker images on aarch64 infrastructure.
What is at stake
Nine of 141 aarch64 release candidates failed after a dependency update. You must weigh a fast dependency pin against a Nix correction that keeps later releases repeatable.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- release date vs repeatable packaging
- small diff vs durable diagnosis
- self-hosted urgency vs release confidence
Why Supabase
Supabase Postgres Docker images are a deployment path for self-hosted customers who need timely PostgreSQL updates.
Written with these in mind
Not your kind of problem? 19 more at Supabase, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.