GA promote (no rebuild): retag :latest to the RC digest + manual dispatch (Plan 2)#148
Merged
Conversation
…); manual dispatch; php85 SSM
… the RC digest instead)
…C) version; fix step name
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.
Summary
Plan 2 of the build-once-promote redesign. Makes GA of
simplerisk-minimala promotion of the already-built RC digest — no rebuild — building on Plan 1 (#147, merged totesting).Design + plan (code-development
docs/superpowers/):specs/2026-07-10-release-image-promotion-design.md,plans/2026-07-10-docker-ga-promote-no-rebuild.md.What changed (3 commits)
promote-latest.yml— now a manualworkflow_dispatch(no auto-promote on push). It (1) verifies the RC<V>-php85tag exists, (2) currency-guards it (its digest must equal the floating:testingdigest, so a stale committed version / stale dispatch ref can't promote an old release to prod), (3) retags DockerHub:latest→ the<V>-php85digest viadocker buildx imagetools create(multi-arch preserved, no build step), and (4) sets prod SSM/simplerisk/customers/image-tag/latest = <V>-php85.push-to-dockerhub.yml— removed the twosimplerisk-minimal-*jobs, so the master push no longer rebuilds the minimal image (full-stacksimpleriskjammy/noble still rebuild). The minimal<V>/<V>-php8xtags come only from Plan 1's testing build;:latestmoves only via the manual promote.What is intentionally NOT changed
push-to-gh-pkgs.yml) keeps its independent minimal rebuild (out of build-once scope; nothing internal uses it).simpleriskkeeps its master-push rebuild.Validation
actionlint(promote-latest, push-to-dockerhub) — clean.Notes
testing → masterpromotes them. This PR lands them ontestingfirst, consistent with Build-once RC publish: immutable php83/84/85 + bare + :testing (Plan 1) #147.20260709-001landing), which asserts:latestand:testingresolve to the same digest after promotion.🤖 Generated with Claude Code