Require dataplicity-release-bot for CI GitHub tokens - #45
Merged
Conversation
HOMEBREW_TAP_TOKEN and WINGET_TOKEN must belong to dataplicity-release-bot; workflows now fail closed if a personal account PAT is configured.
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
HOMEBREW_TAP_TOKEN/WINGET_TOKENmust be owned bydataplicity-release-botscripts/verify-release-bot-token.shand fail closed in Homebrew/WinGet workflows.github/RELEASE_TOKENS.mdNotes
HOMEBREW_TAP_TOKENon this repo has been rotated to the release-bot tap PATWINGET_TOKENstill needs a bot-owned PAT if audit failsTest plan