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
In fact, the checksum was changed earlier today as seen in the above issue, though that change was rolled back. Please consider releasing an archive under /archive/refs/tags/$tag, which its SHA256 value is promised to be stable.
The text was updated successfully, but these errors were encountered:
Maybe we should just use git_repository instead of http_archive in the README? We don't currently do fixed releases here, so I'm not sure we want to start promising them.
git_repository is unideal in many circumstances, since it doesn't support repository caching and it requires downstream users to have git installed (especially problematic for CI / docker container builds). The Bazel team also recommends using http_archive instead.
Per bazel-contrib/SIG-rules-authors#11, the checksum of repository code download archives (https://github.com/google/bazel-common/archive/_COMMIT_.zip) are not stable.
In fact, the checksum was changed earlier today as seen in the above issue, though that change was rolled back. Please consider releasing an archive under
/archive/refs/tags/$tag
, which its SHA256 value is promised to be stable.The text was updated successfully, but these errors were encountered: