Repository navigation
Publish only from main through the docker-hub environment; tag verified digests - #16
Merged
Merged
Conversation
…ed digests - Manual runs of the publish workflow are limited to main, publish runs do not overlap, and the README sync runs only on main. - Jobs that use Docker Hub secrets run in the docker-hub environment. - Runtime and dev images are pushed by digest; that digest is smoke tested (amd64) and Trivy-scanned (amd64 and arm64) before any tag is moved. The dev image builds on the verified runtime digest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016ZbncuXneGAhsgTaizfjVi
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.
Draft: waiting for a maintainer decision. This changes the release process.
Who can publish
publish-docker.yml: aworkflow_dispatchrun publishes only when started frommain. Aconcurrencygroup per ref, without cancelling, stops two publish runs from overlapping.docker-hub-readme.yml: runs only onmain.environment: docker-hub: the runtime/dev publish job, the CI image build and merge jobs, and the README sync.What gets published
imagetools createmoves the tags only after those pass.FROM laravoltdev/image@<runtime digest>rather than a moving tag. It is pushed by digest, scanned for both architectures, and then tagged.Before merging, an owner has to do this in repository settings:
docker-hubenvironment with required reviewers, and restrict it tomainand release tags.DOCKER_HUB_USERNAME,DOCKER_HUB_ACCESS_TOKENandDOCKER_HUB_README_TOKENinto that environment.Not tested here: the publish workflow does not run on pull requests, and the audit host has no Docker. The first run after merge should be a manual run from
main, watched closely. A failed check leaves only an untagged digest behind and no tag moves. The CI image (php8.5-ci) still has no Trivy step; that is a follow-up.🤖 Generated with Claude Code
https://claude.ai/code/session_016ZbncuXneGAhsgTaizfjVi