normalize dropshot dependencies #917
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some recent packages used slightly different dropshot dependencies. The internal-dns one was a particular problem because it didn't have the branch name in it. This results in two entries for dropshot in Cargo.lock, and causes
cargo update -pto not work for updating Dropshot. I suspect this is why we haven't been getting dependabot updates for Dropshot.After this lands, I will poke Dependabot to see if that fixed it.