Repository navigation
fix: release workflow must grant permissions the build workflow requests - #111
Merged
Merged
Conversation
PR build artifact
Firmware patches includedOpenCentauri Firmware Build
Build metadata
Patches applied (TY Sims!)
Please provide feedback as comments in this PR or in the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The v0.5.0 tag run failed with
startup_failureand zero jobs.Cause:
build.yaml(called byrelease.yamlviauses:) now declaresissues: writeandpull-requests: writefor the PR build-summary comment, but the caller only grantedcontents,id-token,attestations. A reusable workflow cannot request permissions the caller does not grant, so GitHub rejected the run before starting any job.Fix: grant the two scopes in
release.yaml.After merge, tag
v0.5.0must be moved to the new main commit and re-pushed to re-trigger the release.