Repository navigation
fix(self-host): pin the compose Postgres image by version and digest - #606
Merged
TheGreatAxios merged 1 commit intoOct 25, 2026
Merged
Conversation
TheGreatAxios
force-pushed
the
cl-11457-build-the-hub-image-locally-by-default-when-self-hosting
branch
4 times, most recently
from
October 25, 2026 15:04
dc31463 to
93adadb
Compare
TheGreatAxios
force-pushed
the
cl-11418-pin-the-compose-files-images-by-digest
branch
from
October 25, 2026 15:18
817bf59 to
56ae8f3
Compare
TheGreatAxios
force-pushed
the
cl-11457-build-the-hub-image-locally-by-default-when-self-hosting
branch
from
October 25, 2026 15:21
93adadb to
4e98cae
Compare
TheGreatAxios
force-pushed
the
cl-11418-pin-the-compose-files-images-by-digest
branch
from
October 25, 2026 15:21
56ae8f3 to
4197a72
Compare
TheGreatAxios
force-pushed
the
cl-11457-build-the-hub-image-locally-by-default-when-self-hosting
branch
from
October 25, 2026 15:28
4e98cae to
da6757f
Compare
TheGreatAxios
force-pushed
the
cl-11418-pin-the-compose-files-images-by-digest
branch
from
October 25, 2026 15:28
4197a72 to
0af87c2
Compare
TheGreatAxios
changed the base branch from
cl-11457-build-the-hub-image-locally-by-default-when-self-hosting
to
main
October 25, 2026 15:32
TheGreatAxios
marked this pull request as ready for review
October 25, 2026 15:32
Contributor
|
Triage: Pass No changes needed from you. A maintainer will review this pull request. Triage will approve. |
TheGreatAxios
changed the base branch from
main
to
cl-11457-build-the-hub-image-locally-by-default-when-self-hosting
October 25, 2026 18:42
![corbits-triage[bot]](https://avatars.githubusercontent.com/u/275831056?s=60&v=4){kind=small}
TheGreatAxios
force-pushed
the
cl-11457-build-the-hub-image-locally-by-default-when-self-hosting
branch
from
October 25, 2026 20:23
da6757f to
85db7a7
Compare
TheGreatAxios
force-pushed
the
cl-11418-pin-the-compose-files-images-by-digest
branch
from
October 25, 2026 20:24
0af87c2 to
373e216
Compare
TheGreatAxios
changed the base branch from
cl-11457-build-the-hub-image-locally-by-default-when-self-hosting
to
main
October 25, 2026 20:29
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Stacked on #604.
compose.yml: Postgres ispostgres:17.11@sha256:b8faeff7712663c2773a190181e1246e37e364b887611c04658c28b44e2408fe, the same Debian 17 image as before, at its newest minor, pinned to its multi-arch index digest (read anonymously from the Docker Hub registry API). The volume mount is unchanged.tooling/exact-deps-check.ts: everycompose*.ymlservice that pulls its image (nobuild) must name amajor.minorversion and asha256digest, orbun run checkfails.Verification
bun tooling/exact-deps-check.tsfails onpostgres:17, on a major-only tag with a digest and on a version without a digest; passes on the pinned image.bun install --frozen-lockfile,bun run check,bun run lintpass.docker compose config: the pinned image and/var/lib/postgresql/data. The Docker daemon does not answer, so nothing was pulled or started.Closes CL-11418