You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently came across this nice extension and really would love to use it more.
However, I frequently have to revisit some dependencies I'd like to upgrade due to them claimed to be incompatible. There is even a switch to control whether or not such upgrades are allowed.
What does it mean if something is judged to be incompatible? Most updates worked for me just fine when forced.
Unfortunately, I couldn't find any documentation or explanation on this. Ideally, this would be covered by the help text, but adding some section to README.md would be helpful too.
The text was updated successfully, but these errors were encountered:
Incompatible according to semver. In merging this into cargo, we're considering using the flag --breaking to specifically indicate "packages marked as breaking compatibility according to semver" as "incompatible" can also mean "incompatible with this version requirement" which we aren't doing.
Thank you for the quick reply and the explanation.
It is nice to know that now, but I think it should be documented somewhere else, e.g. in the help text.
Maybe the output could be more specific on that? Most of the direct upgrades stood within their SemVer bounds, so telling some examples of transitive dependencies that would have a major upgrade would have helped.
I recently came across this nice extension and really would love to use it more.
However, I frequently have to revisit some dependencies I'd like to upgrade due to them claimed to be incompatible. There is even a switch to control whether or not such upgrades are allowed.
What does it mean if something is judged to be incompatible? Most updates worked for me just fine when forced.
Unfortunately, I couldn't find any documentation or explanation on this. Ideally, this would be covered by the help text, but adding some section to
README.md
would be helpful too.The text was updated successfully, but these errors were encountered: