Fix Charmhub release workflow - #43
Merged
Merged
Conversation
The first release run failed with 'Resource not accessible by integration' while creating the git tag with the default read-only token, so only one of the four charms was uploaded. Grant the job contents write access, pin charmcraft to 4.x/stable to match CI, and add workflow_dispatch so a failed release can be retried without a new commit. Signed-off-by: Seyeong Kim <seyeong.kim@canonical.com>
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
1 participant
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 first release run (29998396361) stopped after uploading one of four charms: creating the git tag failed with "Resource not accessible by integration" because the default token is read-only.
contents: writeworkflow_dispatchso a failed release can be retried without a new commit