Update rules_docker dep to v0.17.0 #763
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The last
rules_dockerdep update was to avoid an issue where a transitive dependency resulted in inconsistent GitHub archive downloads and mismatched SHAs when depending on them in Bazel (more info kubernetes/kubernetes#99376).This change has since been incorporated in a real
rules_dockerrelease, v0.17.0, which this PR updates to. Depending on a real release seems safer than depending on some random commit in the rules_docker repo.v0.17.0 currently points to bazelbuild/rules_docker@881e779