Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
add `--dry-run` option to cargo update #6371
This is just an idea, but what if we had a
Context: at ferrous-systems, we put together a small tool to review the source code changes between different versions of the same crate. This obviously was inspired by the most recent npm incident. While implementing the tool, I thought that having
Added the test.
Should we feature gate this? I'd say no: this is more-or-less UI-only features, so there's no new functionality to stabilize, and feature gate would seem like a procedural overhead. But of course adding a feature gate is not a big deal, will gladly do that if necessary.
Team member @withoutboats has proposed to merge this. The next step is review by the rest of the tagged teams:
No concerns currently listed.
Once a majority of reviewers approve (and none object), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!
See this document for info about what commands tagged team members can give me.