ci: standardise release PAT secret name (RELEASE_PLEASE_TOKEN) - #14
Merged
Conversation
operatorhub-submit.yaml already used RELEASE_PLEASE_TOKEN. Standardise on that name so a single PAT works across all three release workflows. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
stubbi
enabled auto-merge (squash)
May 13, 2026 06:49
Default setup was enabled after the repo went public. The two cannot coexist — uploading SARIF from the custom workflow returns "CodeQL analyses from advanced configurations cannot be processed when the default setup is enabled". Drop the custom workflow; default setup covers Go scanning and reports through the Security tab. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.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.
Summary
release-please.yamlandrelease.yamlreferencedsecrets.RELEASE_PATwhileoperatorhub-submit.yamlusedsecrets.RELEASE_PLEASE_TOKEN. The latter is the name documented in the v1 PR description and the one already added to repo secrets, so standardise on it.Without this rename,
release-pleasefails immediately withInput required and not supplied: tokenand never opens the v0.1.0 release PR.Test plan