Supported patched standard PostgreSQL image for local CLI 2.118.0 on arm64
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- docker, postgresql, typescript
Research direction
Start with nix/config.nix and the CLI 2.118.0 image selection, then verify the cited PostgreSQL 17.11 tags and arm64 manifests across the registries named in the issue. Check whether a supported CLI release or per-project pin procedure exists, and whether the current default image includes the fixes. Done means a documented supported tag or digest, pin path, or evidence that no supported option exists.
Written by the indexing model from the issue text.
Description
CLI 2.118.0 selects supabase/postgres:17.6.1.171 for a local PostgreSQL 17 project. The September 25 security advisory describes fixes in PostgreSQL 17.11. GitHub has a standard 17.11.0.001 source release with upstream 17.11 in nix/config.nix, but manifest lookup for that exact standard tag failed on Docker Hub, public ECR and GHCR. A Docker Hub name=17.11 tag query returned only OrioleDB variants.
Which official standard PostgreSQL image tag/digest supports linux/arm64, contains those security fixes, and is compatible with local Supabase CLI? Is there a supported CLI release or per-project pin procedure for it? Alternatively, is there patch/backport evidence for the CLI's current default image?
We have not started this local stack and are not requesting a custom build or an engine change. These observations do not assert that any hosted project is vulnerable.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 526
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 307
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/cli
-
🐛 Bug supabase/cli
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
SQL statement splitter breaks E'...' strings that contain a backslash-escaped quotePossibly taken @7ttp claimed this 1 day ago. Open🐛 Bug supabase/cli
supabase/cli#6885 · 1 assignee ·
Maintainers usually reply within 1 day
-
db push applies migrations when the confirmation answer is not yes or noPossibly taken @7ttp claimed this 2 days ago. Open🐛 Bug supabase/cli
supabase/cli#6869 · 1 assignee ·
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pingdotgg/t3code#14452 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
solana-foundation/program-examples#747 · 1 comment ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
remotion-dev/remotion#11847 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openwatersio/slackwater#355 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melgarafael/DeskcommCRM#1998 · 3 comments ·
Maintainers usually reply within 1 day