Commit f0f56e1
committed
Make sure we are using synchronized versions of LinkML packages.
Some of the Python dependencies we need to run workflows are themselves
dependent on LinkML, which means they cause the installation of both
`linkml` and its dependency `linkml-runtime`.
It seems that these two packages must always be kept "in sync", but
there are no explicit constraints in either of them to enforce that.
So, we can end up `linkml` version 1.9.5 coupled with `linkml-runtime`
version 1.10.0. That combination is perfectly valid according to the
various version constraints (there is _no_ formal constraint that
`linkml` 1.9.5 must use `linkml-runtime` < 1.10.0 -- and unless I missed
something there is also no warning in the documentation that users
should take care of always using the same version of these two
packages), but it is broken in practice, because of some breaking
changes that happened in `linkml-runtime` 1.10.0 (removal of a
`Format.JSON` enumeration value).
Sigh. Not only did the LinkML developers remove a public symbol in a
minor release, they did so without so much as a warning in the release
notes. LinkML, I obscenity in the milk of thy callous disregard for
semantic versioning.
So in this commit, we explicitly declare that we require version 1.10.0
at least of _both_ `linkml` and `linkml-runtime`.1 parent 898d9dd commit f0f56e1
1 file changed
Lines changed: 9 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
14 | 14 | | |
15 | 15 | | |
16 | 16 | | |
17 | | - | |
| 17 | + | |
18 | 18 | | |
19 | 19 | | |
20 | 20 | | |
| |||
68 | 68 | | |
69 | 69 | | |
70 | 70 | | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
71 | 79 | | |
72 | 80 | | |
73 | 81 | | |
| |||
0 commit comments