Repository navigation
ci(deps): allow the shrinkwrap workflow to re-dispatch CI - #36
Merged
Merged
Conversation
The push-triggered run on a pre-PR Renovate branch pushed the refreshed shrinkwrap but failed to dispatch ci.yml: creating a workflow_dispatch event needs actions: write, and the job only declared contents: write. #35 hid this because its PR-side shrinkwrap run found the lockfile already refreshed and skipped the dispatch; a pending branch whose PR has not opened yet has no such shortcut.
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.
Summary
One-line follow-up to #34, surfaced by the first live pending-branch run (before #35 opened): the shrinkwrap workflow pushed the refreshed lockfile but failed to re-dispatch CI with
HTTP 403: Resource not accessible by integration. Creating aworkflow_dispatchevent with theGITHUB_TOKENneedsactions: write; the job only declaredcontents: write.#35 masked this because its PR-side run found the lockfile already refreshed and skipped the dispatch entirely; a pending branch whose PR has not opened yet has no such shortcut.
Validation