Russ Cox would like Jeremy Kun to review this change.
.github/workflows/release: grant release-bazel permissions
Trying to fix:
The workflow is not valid.
.github/workflows/release.yml (Line: 46, Col: 26): Invalid secret, BCR_PUBLISH_TOKEN is not defined in the referenced workflow.
.github/workflows/release.yml (Line: 40, Col: 3): Error calling workflow 'google/re2/.github/workflows/release-bazel.yml@932b308415a622428df2187522db1d273e507164'. The nested job 'release' is requesting 'attestations: write, contents: write, id-token: write', but is only allowed 'attestations: none, contents: read, id-token: none'.
I made the secret repo-wide instead of being scoped to the bcr-push environment.
Not 100% sure that will fix that error.
The changes in this CL should fix the second error.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Code-Review | +2 |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
.github/workflows/release: grant release-bazel permissions
Trying to fix:
The workflow is not valid.
.github/workflows/release.yml (Line: 46, Col: 26): Invalid secret, BCR_PUBLISH_TOKEN is not defined in the referenced workflow.
.github/workflows/release.yml (Line: 40, Col: 3): Error calling workflow 'google/re2/.github/workflows/release-bazel.yml@932b308415a622428df2187522db1d273e507164'. The nested job 'release' is requesting 'attestations: write, contents: write, id-token: write', but is only allowed 'attestations: none, contents: read, id-token: none'.
I made the secret repo-wide instead of being scoped to the bcr-push environment.
Not 100% sure that will fix that error.
The changes in this CL should fix the second error.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |