[bug] Chevron versions with prereleases include breaking changes about conan HOT 4 CLOSED

That PR seems to belong to 0.9.0, but Conan 1 is pinning node-semver==0.6.1, because newer versions of that dependency also introduced some potentially breaking changes (and it was also a reason why this responsibility was embedded and developed in Conan 2 as built-in and not externally, to be able to have full control, do bug fixes and protect stability and evolve while not breaking users code)

from conan.

Hi @AshleighAdams

Thanks for your report.

I have just tried it, adding an extra test, and it seems it has been solved in Conan 2.
The issue in Conan 1 is that Conan 1 uses an external library python-node-semver to resolve versions, so it is outside of scope, this is not expected to get any new fixes (also Conan 2 is the mainstream and recommended version nowadays, it was released now more than 1 year ago, most of dev efforts go to it, Conan 1 is in maintenance mode, critical regressions, backports necessary to smooth the migration to 2.0)

Maybe you can try converting the expression to a explicit one with >=xxx <yyyy one.

from conan.

Yeah, that's what we are doing for now, our of curiosity, was this version ever pulled in? podhmo/python-node-semver#40

Not sure if that PR would have fixed the issue or not

from conan.

I understand, feel free to close as wontfix

from conan.