Open
Conversation
davdhacs
force-pushed
the
davdhacs/apollo-ci-latest-tag
branch
from
4258cf5 to
064adca
Compare
On non-PR builds (tag/main pushes), also push a <flavor>-latest tag alongside the versioned tag. This allows consumers to reference a stable floating tag without needing to update on every release. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
davdhacs
force-pushed
the
davdhacs/apollo-ci-latest-tag
branch
from
064adca to
2adceb7
Compare
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Build Images
|
Adds a manually triggered workflow that retags an existing versioned image as stable without rebuilding. Usage: gh workflow run promote-stable.yaml -f version=0.5.7 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Use docker buildx imagetools create for server-side manifest copy instead of pull/tag/push. Run all flavors in one job. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Temporary: adds push tag trigger and shell default for VERSION. Will revert after testing. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Remove temporary push tag trigger used for testing. Keep shell default for VERSION. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
davdhacs
changed the title
Check that the current tag is the highest semver tag reachable from main before pushing latest. This prevents older tags or tags on non-main branches from overwriting the latest images. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
davdhacs
changed the title
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
tommartensen
approved these changes
Apr 10, 2026
porridge
approved these changes
Apr 13, 2026
Contributor
porridge
left a comment
porridge
left a comment
There was a problem hiding this comment.
It would be good to add a short HOWTO describing the new process, to make sure everyone is on the same page (e.g. AFAICT we should only use -latest in PRs against openshift/release that should not be merged, right)?
Contributor
Author
Good point. I'll add a doc. And we can add a check for this into the stackrox step in osci/prow to show up as a github check failure to prevent PRs to release configs(and probably all stackrox configs) from having the "latest" tag. |
Describe the versioned/latest/stable tagging strategy, how to promote to stable, and how prow jobs should reference images in openshift/release. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
Author
|
And to prevent "latest" on the release branch configs: https://github.com/openshift/release/pull/77736/changes#diff-b46f9042e8c7036fccf35cdeab443de14fec0d4b2643500d6854b79363b764fcR773 |
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
3 participants
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
<flavor>-latesttag alongside the versioned tag.<flavor>-stabletag based on a version[default is latest]This allows openshift-release mirror config to reference the floating tags
latestandstable, removing the need to request testplatform review for every version bump.To use this: openshift/release#77606 adds the "-latest"(and -stable) image mirroring into the openshift-release config, and then tests will be able to use a "latest" or "stable" tagged rox-ci-image.
Test plan
🤖 Generated with Claude Code