fix: inherit secrets in reusable workflow#3711
Merged
Merged
Conversation
… in create-cli-release so the post-release job has required secret access
jdodson
approved these changes
May 14, 2026
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
This change updates the release workflow so the reusable Fig autocomplete publish job receives inherited secrets during stable releases, for example. The scope is limited to CI workflow wiring to prevent post-release failures caused by missing secrets.
publish-to-fig-autocompletereusable workflow call.github/workflows/create-cli-release.ymlto includesecrets: inheriton that jobType of Change
Verification
Confirmed the workflow now passes inherited secrets to the reusable
publish-to-fig-autocompletejob.Additional Context
Related Issue
Closes #[Github issue number]