Repository navigation
Build the H3 release the MobilityDB checkout names - #279
Merged
estebanzimanyi merged 1 commit intoNov 19, 2026
Merged
estebanzimanyi merged 1 commit into
estebanzimanyi merged 1 commit into
Conversation
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
deleted the
ci/provision-builds-the-h3-mobilitydb-names
branch
November 19, 2026 17:54
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.
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.