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
If an advisory has a patched version, or a crate is yanked, we emit a "... (try cargo update -p <package_name>)", the problem is that we don't actually do any checking to see if performing that action will fix the issue.
The patched version in the advisory could be unselectable due to the current version constraints in the dependency graph
We already have the registry metadata for every crate in the graph, so it's possible to put in a little more effort here and either show that message if could fix the issue, or else give a more detailed message about why a simple update won't actually work.
The text was updated successfully, but these errors were encountered:
If an advisory has a patched version, or a crate is yanked, we emit a "... (try
cargo update -p <package_name>
)", the problem is that we don't actually do any checking to see if performing that action will fix the issue.We already have the registry metadata for every crate in the graph, so it's possible to put in a little more effort here and either show that message if could fix the issue, or else give a more detailed message about why a simple update won't actually work.
The text was updated successfully, but these errors were encountered: