Upgrade kgx to 2.7.0#200
Merged
Merged
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
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.
Summary
>=2.6.0to>=2.7.0to pick up Fix obograph_source prefix-map destruction and predicate mapping biolink/kgx#548 (ObographSource predicate-mapping fix + prefix-resolution longest-match fix).requires-pythonfrom>=3.9to>=3.10to match kgx 2.7's requirement; CI matrix already starts at 3.10.Notes
This is purely an upstream bump. In the kg-phenio output the immediate visible change should be small (the BFO part_of/has_part shorthand path was already correct in 2.6.0 via a special-case branch). Hygiene improvements from 2.7:
get_element_by_mappingis now called with the CURIE form, allowing IRI-encoded RO predicates that have biolink mappings to resolve correctly.OBO:prefix from shadowing ontology-specific mappings (FBbt, OBA, EMAPA, ...).