Fix release deploy failing on SOPS install#27
Merged
Merged
Conversation
mise-action exports a job-wide GITHUB_TOKEN while setup-sops also passes its own default token input. octokit's auth-action rejects a token specified more than once, crashing the Install SOPS step and failing every release build. Co-Authored-By: Claude Opus 4.8 (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
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
Install SOPSstep (nhedger/setup-sops@v2) was crashing every release build with[@octokit/auth-action] The token variable is specified more than once.jdx/mise-actionexports a job-wideGITHUB_TOKENenv var, andsetup-sopsalso passes its own defaulttokeninput. octokit's auth-action rejects a token specified in more than one place.GITHUB_TOKENenv var for just theInstall SOPSstep, leaving only the action's owntokeninput.🤖 Generated with Claude Code