-
Notifications
You must be signed in to change notification settings - Fork 979
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] conan1: conflict of node-semver==0.6.1 with semver #15210
Comments
Hi @Nekto89 Thanks for your report. It seems this is a conflict of names between Conan 2.0 solve this problem, it has removed |
@memsharded can version of node-semver be bumped in conan1? Or is it too much work and risky? If I understood correctly, "node-semver" has fixed this conflict through rename in 0.9.0 podhmo/python-node-semver#45 |
Yes, it is pinned to that specific 0.6.1 version, because node-semver changed behavior later that would be considered breaking for Conan users (this was also one of the reasons we decided to implement our own functionality in 2.0, to not depend on something external in something as core as this) |
I am closing this, as this cannot be changed in Conan 1 because it would be breaking behavior, and has already been fixed in Conan 2, thanks for the feedback |
Environment details
Steps to reproduce
Expected output: 1.62.0
Logs
The text was updated successfully, but these errors were encountered: