Skip to content

ci: fix miner release proposal workflow token - #608

Merged
n13 merged 1 commit into
mainfrom
grok/fix-miner-release-proposal-token
Aug 14, 2026
Merged

ci: fix miner release proposal workflow token#608
n13 merged 1 commit into
mainfrom
grok/fix-miner-release-proposal-token

Conversation

@n13

@n13 n13 commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

Overview

The Miner - Create Release Proposal run failed at gh label create with HTTP 401: Bad credentials. The job used secrets.PAT_TOKEN, which is expired; git push already succeeded with the default checkout token.

What changed

  • Use secrets.GITHUB_TOKEN with the job's existing contents: write / pull-requests: write permissions.
  • Stop creating labels in CI. miner-release-proposal, automated, and draft-release already exist on the repo.
  • Reuse the release branch/PR on re-run (checkout -B, --force-with-lease, gh pr edit if a PR already exists).

Validation

  • Confirmed the failed step was gh label create against PAT_TOKEN.
  • Labels created on the repo: miner-release-proposal, automated, draft-release.
  • Re-run of Miner - Create Release Proposal after merge should open the version-bump PR.

Risks and mitigations

  • Default GITHUB_TOKEN events do not trigger other workflows. A human merge of the proposal PR still fires Miner - Publish Release.
  • release/miner-v0.6.1 already exists from the failed run; the workflow now resets it with --force-with-lease.

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.
@n13
n13 merged commit ae92689 into main Aug 14, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant