Skip to content

Build the H3 release the MobilityDB checkout names - #279

Merged
estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:ci/provision-builds-the-h3-mobilitydb-names
Nov 19, 2026
Merged

estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:ci/provision-builds-the-h3-mobilitydb-names

Conversation

@estebanzimanyi

Copy link
Copy Markdown
Member

MobilityDB supports one H3 release, H3_REQUIRED_VERSION of its top-level CMakeLists.txt, and its configure refuses any other; its .github/scripts/install-h3.sh builds that release from its tag. provision-meos installed libh3-dev, whichever release the PostgreSQL archive carries (4.5.0), so every libmeos build of the action stops at configure since MobilityDB pinned 4.6.0. The action takes H3 from the checkout's own script when the checkout carries it: it builds the release into a prefix cached by its version and installs it under /usr/local, where MobilityDB's CMake and the catalog parse find it, as GDAL is; a checkout predating the script takes the package as before.

Witness: the tests job of MEOS-API #278 stops at "MobilityDB requires H3 4.6.0, but the header found at /usr/include/h3/h3api.h is H3 4.5.0" (run 44578447526), after installing libh3-1 4.5.0-1.pgdg26.04+1.

Why: every consumer of provision-meos builds libmeos through it, MEOS-API's tests, GoMEOS, MobilityDuck's refresh and the JVM bindings among them.

MobilityDB supports one H3 release, H3_REQUIRED_VERSION of its top-level CMakeLists.txt, and its configure refuses any other; its .github/scripts/install-h3.sh builds that release from its tag. provision-meos installed libh3-dev, whichever release the PostgreSQL archive carries (4.5.0), so every libmeos build of the action stops at configure since MobilityDB pinned 4.6.0. The action takes H3 from the checkout's own script when the checkout carries it: it builds the release into a prefix cached by its version and installs it under /usr/local, where MobilityDB's CMake and the catalog parse find it, as GDAL is; a checkout predating the script takes the package as before.

Witness: the tests job of MEOS-API MobilityDB#278 stops at "MobilityDB requires H3 4.6.0, but the header found at /usr/include/h3/h3api.h is H3 4.5.0" (run 44578447526), after installing libh3-1 4.5.0-1.pgdg26.04+1.

Why: every consumer of provision-meos builds libmeos through it, MEOS-API's tests, GoMEOS, MobilityDuck's refresh and the JVM bindings among them.
@estebanzimanyi
estebanzimanyi merged commit 874a847 into MobilityDB:master Nov 19, 2026
2 checks passed
@estebanzimanyi
estebanzimanyi deleted the ci/provision-builds-the-h3-mobilitydb-names branch November 19, 2026 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant