Repository navigation
Publish the image to GHCR with signed build provenance - #95
Merged
Merged
Conversation
The image was pushed to a personal Docker Hub account with a long-lived access token stored as a repository secret. EnzymeAD has no Docker Hub presence but already publishes its container images on the GitHub Container Registry, so the image moves to ghcr.io/enzymead/reactantserver. The workflow now logs in with the run's own GITHUB_TOKEN, so the DOCKERHUB_* variable and secrets are no longer used and can be deleted. The owner in the path is the repository's, lowercased, so a fork publishes to its own namespace instead of failing against EnzymeAD's. After the push, actions/attest (pinned to v4.2.2 by SHA, like the other actions) records SLSA build provenance for the pushed digest: this repository, commit, workflow and run built it. It is signed through Sigstore with the run's OIDC identity, so there is no signing key to hold or rotate, and it is stored with GitHub and pushed beside the image. The build is not bit-for-bit reproducible (the precompile caches differ between builds), so rebuilding from source cannot confirm a published digest; the attestation is what ties a digest to its source. Consumers check it with `gh attestation verify oci://ghcr.io/enzymead/reactantserver:latest --repo EnzymeAD/ReactantServer.jl`, which the deployment docs and deploy/README.md now describe, along with pinning by digest. The job gains packages, id-token, attestations and artifact-metadata write permissions; the workflow-level default stays contents: read. The image name changes everywhere the docs, README, compose default and deploy/ comments named it. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.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.
The image was pushed to a personal Docker Hub account with a long-lived access token stored as a repository secret. EnzymeAD has no Docker Hub presence but already publishes its container images on the GitHub Container Registry, so the image moves to ghcr.io/enzymead/reactantserver. The workflow now logs in with the run's own GITHUB_TOKEN, so the DOCKERHUB_* variable and secrets are no longer used and can be deleted. The owner in the path is the repository's, lowercased, so a fork publishes to its own namespace instead of failing against EnzymeAD's.
After the push, actions/attest (pinned to v4.2.2 by SHA, like the other actions) records SLSA build provenance for the pushed digest: this repository, commit, workflow and run built it. It is signed through Sigstore with the run's OIDC identity, so there is no signing key to hold or rotate, and it is stored with GitHub and pushed beside the image. The build is not bit-for-bit reproducible (the precompile caches differ between builds), so rebuilding from source cannot confirm a published digest; the attestation is what ties a digest to its source. Consumers check it with
gh attestation verify oci://ghcr.io/enzymead/reactantserver:latest --repo EnzymeAD/ReactantServer.jl, which the deployment docs and deploy/README.md now describe, along with pinning by digest.The job gains packages, id-token, attestations and artifact-metadata write permissions; the workflow-level default stays contents: read. The image name changes everywhere the docs, README, compose default and deploy/ comments named it.