Track upstream master for the MEOS derivation#10
Merged
estebanzimanyi merged 1 commit intoJul 16, 2026
Conversation
Provision the MEOS catalog and libmeos from upstream MobilityDB master via the shared provision-meos action (mobilitydb-ref: master), and drop the pinned tools/meos-source-commit.txt. Tracking master keeps the source, the derived catalog and the native library the binding is generated against moving together.
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.
Provision the MEOS catalog and libmeos from upstream MobilityDB
mastervia the sharedprovision-meosaction (mobilitydb-ref: master), and drop the pinnedtools/meos-source-commit.txt.Tracking master (not a pinned commit) keeps the source, the derived catalog and the native library the binding is generated against all moving together, so the catalog and the
run.pythat derives it never drift apart. This mirrors the track-master rollout already merged for the JVM bindings (MobilitySpark, MobilityFlink, MobilityKafka).