Repository navigation
ci: publish through the shared ci-components workflow - #12
Merged
Merged
Conversation
The build/publish/sign jobs now live in one place for every repository that publishes this way. Same behaviour: build without credentials, publish without repository code, keyless cosign, <sha>-<UTC> tags. The repository passes its own workload identity provider, publisher SA and image from repository variables.
gerau
self-requested a review
October 29, 2026 14:56
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.
Follow-up to #10. The image build + publish job moves into the shared reusable workflow
Blockstream/ci-components/.github/workflows/publish.yml@v1, so it is maintained in one place for all repositories that publish this way.The behaviour stays the same:
buildbuildsdeployment/Dockerfile.relaywithout credentials or OIDC.publish(environmentstaging) runs no repository code. It pushes only the OCI data frombuildand signs the digest with keyless cosign.<commit sha>-<UTC timestamp>.This also fixes the failed publish after #10 (
invalid_target/ not authorized). The registry federation now accepts only this shared workflow for this repository.The repository variables that are already set (
GCP_WORKLOAD_IDENTITY_PROVIDER,GCP_SERVICE_ACCOUNT,IMAGE_NAME) stay as they are; the workflow now passes them to the shared workflow as inputs. The build job runs in astaging-buildenvironment, which GitHub creates on the first run. It needs no settings.After merge, the publish run on
mastershould produce the first image.