Widen omop-alchemy, oa-configurator, and omop-emb pins to semver ranges#33
Open
nicoloesch wants to merge 3 commits into
Open
Widen omop-alchemy, oa-configurator, and omop-emb pins to semver ranges#33nicoloesch wants to merge 3 commits into
nicoloesch wants to merge 3 commits into
Conversation
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.
Now that #28 put this repo and its upstream packages on label-driven semver, replaces exact pins with
>=current,<next-majorranges across all three sibling deps (omop-alchemy,oa-configurator,omop-emb, including thefaiss-cpu/pgvectorextras). Also aligns thedevextra'soa-configurator[postgres]floor with the main pin, and makes thepostgresextra'somop-alchemy[postgres]bound explicit. Verified viauv lockthis was already effectively bounded through the main deps entry (PEP 508 resolvers merge multiple requirement lines for the same package), so this is a readability change, not a functional one.Also installs the
cava-devopspre-commit hook so future dependency edits keepuv.locksurgically in sync without relying on memory:Notes
CI on this PR will fail until cava-devops PR AustralianCancerDataNetwork/cava-devops#2 merges to main
ci.ymlhere already points at@mainfor the--frozen-basedbuild-test.yml, which doesn't exist there yet. This is expected and will resolve on its own once that PR merges; no action needed here beyond waiting.