Pin the MEOS source commit for provision-meos#10
Merged
estebanzimanyi merged 1 commit intoJul 15, 2026
Conversation
Record the upstream MobilityDB commit in tools/meos-source-commit.txt and have CI read it to feed provision-meos, so the derived catalog and the libmeos build stay in lockstep with one pinned surface. This matches the Spark/Flink/Kafka bindings, giving every provision-meos consumer the same way to select the MEOS source — a single-file edit to bump it.
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
1 participant
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
Record the upstream MobilityDB commit in
tools/meos-source-commit.txtand have CI read it via aResolve the MEOS source commitstep, passing the resolved SHA toprovision-meosasmobilitydb-ref.Why
The
provision-meosconsumers select their MEOS source two different ways: Spark/Flink/Kafka pin a commit intools/meos-source-commit.txt, while this binding tracksmasterinline in the workflow. This change moves the binding onto the pinned-commit method so everyprovision-meosconsumer selects the MEOS source the same way — the derived catalog and the libmeos build come from one recorded commit, and bumping the surface is a single-file edit with no SHA duplicated across steps.The pin equals the current MobilityDB
masterHEAD, so the derived catalog and libmeos are the same as before; only the way the source commit is selected changes.