Skip to content

fix(ci): sign in the gated job so it can read the production env secret#31

Merged
jhumel-code merged 1 commit into
mainfrom
cf/publish-secret-scope
Jun 16, 2026
Merged

fix(ci): sign in the gated job so it can read the production env secret#31
jhumel-code merged 1 commit into
mainfrom
cf/publish-secret-scope

Conversation

@jhumel-code

Copy link
Copy Markdown
Collaborator

The Sign step ran in the un-gated build job, but RULES_SIGNING_KEY_ED25519 is a production-environment secret — env secrets are only readable by a job that declares the environment. So the build job would see an empty secret and the first publish fails at sign (secret not set).

Fix: move environment: production onto the build job (the one that signs). The whole signed publish now waits for the required-reviewer approval before anything is signed/released; promote runs after the gated, self-verified build, so the channel re-point stays gated without a second approval. Caught while validating the pipeline after the engine merge; the ci-workflow audit lens had been throttled before it could verify this. (TR-323)

🤖 Generated with Claude Code

RULES_SIGNING_KEY_ED25519 is a production-environment secret, but the Sign step
ran in the un-gated build job — environment secrets are only readable by a job
that declares the environment, so the build job saw an empty secret and the first
publish would fail at sign ('secret not set'). Move environment: production onto
the build job (which signs); promote runs after the gated, self-verified build, so
the channel re-point stays behind the required-reviewer approval. (TR-323)
@jhumel-code jhumel-code merged commit 800c2d2 into main Jun 16, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant