You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9beeb3b
Browse filesBrowse the repository at this point in the historyBrowse files
Switch Docker image matrices to PostgreSQL 17/18 and adopt tools v0.8.39
Activates the PostgreSQL 18 image, retires PostgreSQL 16, and moves every
workflow onto the tools tag that matches.
Matrices (cron, on_push, on_tag) change postgres_16 -> postgres_18. The
pg18 tag has never been published even though pkgvars has carried
postgres_18_version since February; this closes that gap. PostgreSQL 16 is
dropped because Citus no longer supports it, which is also why the nightly
package builds have been failing on almalinux-8-pg16.
The tools pin moves to v0.8.39 in all five workflows (four were on v0.8.38,
update_version.yml was still on v0.8.36). This is not optional: v0.8.39
removes postgres_14, postgres_15 and postgres_16 from DockerImageType, so
the pin bump and the matrix change have to land together or the
postgres_16 job fails on an invalid enum value.
postgres-18/Dockerfile moves from Citus 14.1.0 to 14.2.0 so the newly
published pg18 tag matches latest and pg17 rather than shipping an older
Citus. All three pinned packages are published for PostgreSQL 18:
postgresql-18-citus-14.2=14.2.0.citus-1, postgresql-18-hll=2.21.citus-1
and postgresql-18-topn=2.7.1.citus-1.
postgres_19 is deliberately not added to the matrices. PostgreSQL 19 is
still 19beta3 and no postgresql-19-citus package exists, so the image
cannot build yet. postgres-19/Dockerfile stays in the tree, unreferenced,
and update_version.yml will refresh it on the next version bump now that
the pin supports postgres19.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 1ed7b58a-0ba9-4f47-a1de-3ee665bae7f2
0 commit comments