Switch from sha256
to integrity
in release notes
#2389
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.
integrity
is preferred because it works for bothhttp_archive
(legacy) andarchive_override
(bzlmod).sha256
only works forhttp_archive
. Context: bazelbuild/bazel#20156I confirmed that
xxd
andbase64
commands are available in the GitHub ubuntu-20.04 runner:and that this produces an integrity string that checks out with what Bazel wants. See dtolnay/cxx@17f46ec for a successful use of
integrity
withhttp_archive
:and dtolnay/cxx#1294 for a successful use of
integrity
witharchive_override
.sha256
does not work inarchive_override
.