Skip to content

Commit 6569a9a

Browse files
committed
.github/workflows/release-bazel: disable attestation
The bazel attestations are too complicated for mortals like me. Change-Id: I28e05de4ca3391fd9c87189ff3be3aeedea95ac4
1 parent 0f6c07e commit 6569a9a

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

.github/workflows/release-bazel.yml

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,10 +21,17 @@ jobs:
2121
uses: bazel-contrib/publish-to-bcr/.github/workflows/publish.yaml@v0.2.2
2222
with:
2323
tag_name: ${{ inputs.tag_name }}
24-
# This workflow seems to require keeping a fork of the upstream to open
25-
# PRs from.
2624
registry_fork: re2-machine/bazel-central-registry
27-
attest: true
25+
# NOTE: To use attest: true, we need a signed intoto.jsonl file,
26+
# but that appears to require using
27+
# the release_ruleset support described on
28+
# https://github.com/bazel-contrib/publish-to-bcr?tab=readme-ov-file#attesation-support
29+
# but that requires a release_prep.sh file,
30+
# and an override on the test command,
31+
# and may insist on doing the release upload of the source zip
32+
# (which we do ourselves separately),
33+
# and possibly more problems I didn't hit because I gave up.
34+
attest: false # too hard to generate the intoto.jsonl file
2835
permissions:
2936
contents: write
3037
id-token: write

0 commit comments

Comments
 (0)