bazel-lib/e2e/coreutils
Alex Eagle 4ad02b7795
refactor(release): switch release integrity to be dynamic (#854)
* refactor(release): switch release integrity to be dynamic

This matches rules_py as documented by
https://blog.aspect.build/releasing-bazel-rulesets-rust

It has the benefit that developers no longer get yelled at to vendor some updated integrity hashes into bazel-lib every time they touch the Go sources.

* refactor: echo should produce trailing newline

* chore: bump action-gh-release to avoid Node 16 warning

* chore: update test that is sensitive to compilation mode

We now only use --compilation_mode=opt when cutting a release
2024-05-23 16:08:35 -07:00
..
.bazeliskrc chore: green up Windows CI (#643) 2023-11-07 14:01:45 -08:00
.bazelrc chore: align ci patterns (#843) 2024-05-13 23:51:10 -07:00
.bazelversion chore: use coreutils hashsum (#333) 2023-03-10 20:37:57 +03:00
BUILD.bazel fix: remove need for rules_go when depending on a bzl_library target (#663) (#664) 2023-11-16 14:26:40 -08:00
MODULE.bazel chore: align ci patterns (#843) 2024-05-13 23:51:10 -07:00
WORKSPACE refactor: rework toolchain registration for WORKSPACE and bzlmod users (#597) 2023-10-10 12:16:13 -07:00
WORKSPACE.bzlmod chore: use coreutils hashsum (#333) 2023-03-10 20:37:57 +03:00
ls.txt.expected chore: use coreutils hashsum (#333) 2023-03-10 20:37:57 +03:00
md5.txt refactor(release): switch release integrity to be dynamic (#854) 2024-05-23 16:08:35 -07:00
sha1.txt refactor(release): switch release integrity to be dynamic (#854) 2024-05-23 16:08:35 -07:00
sha256.txt refactor(release): switch release integrity to be dynamic (#854) 2024-05-23 16:08:35 -07:00
test.bin chore: use coreutils hashsum (#333) 2023-03-10 20:37:57 +03:00