Bump docker to version 14.2.0 - #385
Merged
Merged
Conversation
Bump Citus to 14.2.0 across all image variants (latest/PG18, pg17, pg16, alpine). Also bump the PostgreSQL 17 base image to 17.10 and the PostgreSQL 16 base image to 16.14. These are the PG minors Citus 14.2.0 was built and tested against, as pinned on the release-14 branch of citusdata/the-process (circleci/images/PG_VERSIONS) at the time of the 14.2.0 release. The PG18 base stays at 18.4 for the same reason. This part is required, not cosmetic. The Citus 14.2 packages reference the palloc0_mul symbol, introduced in PostgreSQL 17.10 / 16.14 / 18.4, so on the previous 17.6 and 16.10 bases the server aborted at startup with: FATAL: could not load library ".../citus.so": undefined symbol: palloc0_mul Verified by building all four variants and confirming each starts and reports citus extension 14.2-1 on PG 18.4, 17.10, 16.14 and 18.4-alpine. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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
Bump the Citus docker images to 14.2.0 across all variants (latest/PG18, pg17, pg16, alpine).
Citus 14.2.0 was released on 2026-08-06, but no
v14.2.0tag was ever pushed here, so no image was ever built.citusdata/citus:14.2.0is currently missing from Docker Hub.Why the PostgreSQL base images also move
This is required, not cosmetic. A citus-version-only bump builds fine but produces images that will not start on pg17/pg16:
The Citus 14.2 packages are built against newer PostgreSQL minors and reference
palloc0_mul, which was introduced in PostgreSQL 17.10 / 16.14 / 18.4. The previous17.6and16.10bases predate it.The new pins are the minors Citus 14.2.0 was built and tested against, per
circleci/images/PG_VERSIONSon therelease-14branch ofcitusdata/the-processas of the 14.2.0 release (commit7d2c40e3, 2026-05-28):release-14@ 14.2.0Note these are deliberately not the current
release-14HEAD values (16.15 / 17.11 / 18.6) — that bump landed on 2026-08-15, nine days after the 14.2.0 release. Pinning to the release point keeps the images aligned with what the release was validated against, and happens to also be the exact minimum that loadscitus.so.18.4-alpineis still Alpine 3.24.1, so theclang21/llvm21build toolchain needs no change.Validation
All four variants were built locally and smoke tested — container starts,
citusextension is created and reports the right version:Also confirmed
postgresql-{16,17,18}-citus-14.2 = 14.2.0.citus-1is present in the citusdata apt repo (trixie and bookworm), and that thev14.2.0source tarball used by the alpine build resolves.hadolint reports no new findings.
After merge
Push the
v14.2.0tag to triggerpublish_docker_images_on_tag.yml, which builds and publishes the images.Follow-ups (not in this PR)
update_version.ymlisworkflow_dispatch-only and has failed on every recorded run, so version bumps are effectively manual today. That is why 14.2.0 was missed.mastertracks a single Citus line (the Dockerfiles hardcodecitus-<major>.<minor>), and there is no 13.x maintenance branch. Older-line releases have never been published here.