ci: fix miner release proposal workflow token - #608
Merged
Conversation
The proposal workflow failed on label create with 401 because PAT_TOKEN is expired. Apply existing labels with the default token instead, and reuse the release branch/PR if a previous run already pushed it.
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.
Overview
The Miner - Create Release Proposal run failed at
gh label createwithHTTP 401: Bad credentials. The job usedsecrets.PAT_TOKEN, which is expired; git push already succeeded with the default checkout token.What changed
secrets.GITHUB_TOKENwith the job's existingcontents: write/pull-requests: writepermissions.miner-release-proposal,automated, anddraft-releasealready exist on the repo.checkout -B,--force-with-lease,gh pr editif a PR already exists).Validation
gh label createagainstPAT_TOKEN.miner-release-proposal,automated,draft-release.Risks and mitigations
GITHUB_TOKENevents do not trigger other workflows. A human merge of the proposal PR still fires Miner - Publish Release.release/miner-v0.6.1already exists from the failed run; the workflow now resets it with--force-with-lease.