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 would expect that cargo upgrade (a) leaves dependency specifications in the same format as it found them, (b) doesn't change them if the new version if semver-compatible while --skip-compatible is passed.
The text was updated successfully, but these errors were encountered:
This is not what I expected to happen:
I would expect that cargo upgrade (a) leaves dependency specifications in the same format as it found them, (b) doesn't change them if the new version if semver-compatible while --skip-compatible is passed.
The text was updated successfully, but these errors were encountered: