This message was deleted.

If you use simple string notation (without special

!!

marker) it's just

require

(dependency or constraint doesn't matter) which pardon for the pun requires minimal version (or range) for dependency

I'm actually really confused by why the resolution engine would fail here. According to the docs, a

strictly

constraint should override a previously set

requires

, and vice-versa. What am I missing?

It should override on the same MutableVersionConstraint object but in your case there are different constraints from different configurations

sigh. Ok, thanks