馃懛 ci(release): report a missing release token - #692
Merged
Conversation
Every dispatch of the prepare-release workflow since 4.2.0 stopped at checkout with "Input required and not supplied: token", which names neither the secret nor where it belongs. RELEASE_PAT was never added to the release-auth environment, and the same error will come back the day the token expires. Check the secret before checkout so the run says what is missing.
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.
Every dispatch of Prepare release has failed at the checkout step with
Input required and not supplied: token, on 2026-08-08, 2026-08-13 and 2026-08-20. The message names neither the missing secret nor the environment it belongs in, and reaching it costs a dispatch and a look at the log.RELEASE_PATis absent from therelease-authenvironment, and the same failure returns whenever the token expires or gets revoked.A guard ahead of the checkout now reads the secret and stops with
RELEASE_PAT is unset; add it to the release-auth environment, which shows up on the run summary as an annotation. Supplying the token stays a separate step, done in the repository settings.