Repository navigation
ci(secrets): sync protected release credentials - #109
Merged
Merged
Conversation
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.
Why
Deliver the release App credentials through Doppler's native synchronization into the existing main-only release environment.
Pass named secrets only to repository-scoped App token actions after tool setup.
Keep exact-source release qualification and registry authentication.
Changes
The manual verification workflow creates and revokes a read-only token without publishing a package or tag.
The synchronization manifest selects two App fields and binds the numeric repository and owner identities.
The delivery ADR remains proposed.
Closes #105.
Validation
Both
just checkandjust check-workflowspassed on macOS.The gates check formatting, lint, dependency policy, workspace tests, documentation, and workflow contracts.
The workflow security and prose checks passed.
Gitleaks history and staged-diff scans passed.
Pause publishing during the merge and authentication check, then restore its previous workflow state.
Keep the Doppler identity until replacement authentication succeeds for every consumer.
@coderabbitai ignore