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
When upgrading an entire workspace, cargo upgrade first shows Checking virtual workspace's dependencies and goes through those, and then goes through the crates in the workspace. When doing the latter, in verbose mode (which is necessary to see the list of crates that need upgrading) it'll print a warning like warning: ignoring cratename, source is workspace for every workspace dependency.
This warning would be useful if cargo upgrade was only running on a single package in the workspace, to explain why it doesn't upgrade workspace dependencies. However, in the case where cargo upgrade is already looking at workspace dependencies in the same run, it seems unnecessary.
Suggestion: remember if cargo upgrade looked at workspace dependencies before, and if so:
Skip printing this warning
When printing "Checking cratename's dependencies", add "non-workspace" to that line
The text was updated successfully, but these errors were encountered:
Hadn't given the verbose output too much attention. Those messages should likely be switched to log messages.
I also haven't been giving cargo upgrade too much attention, instead encouraging effort towards cargo update --breaking which is now available in nightly
When upgrading an entire workspace, cargo upgrade first shows
Checking virtual workspace's dependencies
and goes through those, and then goes through the crates in the workspace. When doing the latter, in verbose mode (which is necessary to see the list of crates that need upgrading) it'll print a warning likewarning: ignoring cratename, source is workspace
for every workspace dependency.This warning would be useful if cargo upgrade was only running on a single package in the workspace, to explain why it doesn't upgrade workspace dependencies. However, in the case where cargo upgrade is already looking at workspace dependencies in the same run, it seems unnecessary.
Suggestion: remember if cargo upgrade looked at workspace dependencies before, and if so:
The text was updated successfully, but these errors were encountered: