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
..
ci.bazelrc	ci: green up rbe on main (#847)	2024-05-14 07:44:33 -07:00
ci.yaml	chore: align ci patterns (#843)	2024-05-13 23:51:10 -07:00
conventional-commits.yml	refactor: update conventional-commits.yml (#824)	2024-04-29 06:11:29 -07:00
integrity.jq	refactor(release): switch release integrity to be dynamic (#854)	2024-05-23 16:08:35 -07:00
new_issue.yaml	chore(deps): update actions/github-script action to v7 (#759)	2024-02-26 17:34:30 -08:00
release.yml	refactor(release): switch release integrity to be dynamic (#854)	2024-05-23 16:08:35 -07:00
release_prep.sh	refactor(release): switch release integrity to be dynamic (#854)	2024-05-23 16:08:35 -07:00