This message was deleted.

Catalogs support rich versions, not just strings

ah okay. so preferedVersion is what I'm after then when using simple fixed version right?

e.g:

[versions]
my-lib = { require = "[1.0, 2.0[", prefer = "1.5" }

ah yes makes sense

should be

requiredVersion

, not

preferredVersion

makes sense. 👍

IIRC

MutableVersionConstraint

clears required version when the strict one is set and vice versa with preferred complimenting either of them. Not sure in which oredr the catalog parser calls these methods on the mutable constraint when parsing toml though. Standard notation parser parses plain version (or range) as required version and support

!!

token to parse as strict version instead.