ci: wire CASCADE_STATE_TOKEN for protected-trunk state writes - #96
Merged
Merged
Conversation
Set the manifest state_token to the CASCADE_STATE_TOKEN secret and regenerate the self-host orchestrate and promote workflows. Finalize now writes manifest state through the GitHub Contents API with a token that can update the protected trunk, replacing the direct push that branch protection rejected. Signed-off-by: Joshua Temple <joshua.temple@stablekernel.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
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.
Activates the protected-trunk state write added in #94. Sets the manifest
state_tokento theCASCADE_STATE_TOKENsecret and regenerates the self-host orchestrate and promote workflows.With this, the Finalize state write authenticates with a token that can update the protected
mainbranch, so thechore: update state [skip ci]commit lands through the GitHub Contents API instead of the directgit pushthat branch protection was rejecting (GH006: Required status check "PR Gate" is expected). The API-created commit is also signed (Verified).orchestrate.yamlandpromote.yamlnow carryGH_TOKEN: ${{ secrets.CASCADE_STATE_TOKEN }}on their state-write steps.concurrency:block) and keepsactions/checkout@v6(from fix: bump generated checkout pin to v6.0.3 to match committed workflows #95), with no downgrade.This is the commit that should turn the self-host Finalize job green. The first Orchestrate run on
mainafter merge confirms the token can write through branch protection; if it can't, the fallback is a GitHub App on a ruleset bypass.