mirror of
https://github.com/hanzoai/postgres.git
synced 2026-10-30 18:33:07 +00:00
zeekay
53da1d9b88
github.com has no runner for hanzo-build-linux-amd64, so a caller under .github/workflows is a gate that can never be scheduled. This is the ~7-line caller on the plane that can (git.hanzo.ai git-runner fleet), pinned @v1.
24 lines
1.2 KiB
YAML
24 lines
1.2 KiB
YAML
# ghcr.io/hanzoai/sql — PostgreSQL 18 with pgvector, pg_cron, pg_documentdb and
|
|
# this repo's own contrib/zap_fdw. The Dockerfile IS the gate: it compiles
|
|
# zap_fdw from this tree and bakes conf/ and docker-entrypoint-initdb.d/, so a
|
|
# break in any of them fails the build. That is also exactly the path
|
|
# .github/workflows/deploy.yml filters on, and it is a full extension toolchain
|
|
# build (libbson, Intel decimal math, pcre2, documentdb) — slow by nature.
|
|
#
|
|
# version: is required here and cannot be derived. imgver reads a repo's own
|
|
# manifest, and this tree has none it recognises — no package.json, Cargo.toml,
|
|
# VERSION or pyproject.toml — so the first run died with "no version for
|
|
# ghcr.io/hanzoai/sql. We don't ship shas." It tracks PG_MAJOR, which is what
|
|
# the image actually ships: the runtime stage is FROM postgres:18-bookworm.
|
|
# NOT configure.ac's 19beta1 — that is the vendored PostgreSQL source fork,
|
|
# which this image does not build and does not run. imgver takes
|
|
# max(declared, published) + a patch, so the series moves on its own from here.
|
|
#
|
|
# No deploy:. universe pins the live tag.
|
|
version: 18.0.0
|
|
images:
|
|
- name: sql
|
|
context: .
|
|
dockerfile: Dockerfile
|
|
repo: ghcr.io/hanzoai/sql
|