Repository navigation
Copy CLI signing secrets to release environment - #1652
Merged
Merged
Conversation
Co-Authored-By: GPT-6 Sol <noreply@openai.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
The renamed Toolkit repository keeps its
productionenvironment restricted tomain. Its CLI release branches now use a dedicatedcli-releaseenvironment restricted torelease/cli/*.Update the protected, default-branch-only migration workflow to verify the destination repository ID and exact branch policy before copying the five signing/CLI secrets into
cli-release. It no longer rewrites the destination production environment or touches unrelated repository settings.Validation
bash -ncli-releasebranch policy checked through GitHub's APIRun this workflow from
mainonce, verify the five secret names without exposing their values, then remove the temporary migration credential and workflow.