fix(ci): release-please falls back to GITHUB_TOKEN (works without the PAT)#80
Merged
Merged
Conversation
…out the PAT
The mandatory RELEASE_PLEASE_TOKEN made the workflow fail
("Input required and not supplied: token") when the secret is unset, so
release-please couldn't even open its release PR. Fall back to GITHUB_TOKEN:
the release PR + tag are created out of the box; the PAT now only governs
whether the created tag auto-triggers release.yml (PyPI + Docker) — the
already-documented caveat.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HAPB5GA4NVUgKFsVFVJDxN
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-please runs on
mainfailed withInput required and not supplied: tokenbecauseRELEASE_PLEASE_TOKENisn't set, so it couldn't open its release PR at all.Fall back to
GITHUB_TOKEN(secrets.RELEASE_PLEASE_TOKEN || secrets.GITHUB_TOKEN). The workflow already grantscontents: write+pull-requests: write, so with the fallback release-please opens/maintains the release PR out of the box. The PAT now only governs whether the created tag auto-triggersrelease.yml(PyPI + Docker) — the previously-documented caveat (aGITHUB_TOKEN-created tag doesn't fireon: push: tags).actionlintclean.🤖 Generated with Claude Code