[codex] Add BuildKit image release workflow#165
Merged
vigneshrajsb merged 1 commit intomainfrom Apr 15, 2026
Merged
Conversation
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.
Summary
buildkit.Dockerfilefor the custom BuildKit image with the ECR credential helper baked inlifecycleoss/buildkitimages to Docker Hubv0.12.0so rebuilds stay reproducibleWhy
The current BuildKit image setup was a quick patch built and pushed manually to internal ECR. This moves that definition into the repo and gives us a repeatable release path to Docker Hub, aligned with the existing base-image workflow.
Impact
Downstream consumers can switch from the internal ECR-hosted BuildKit image to
lifecycleoss/buildkittags published from source control.Validation
git diff --cached --checkprettier --writeon the workflow during commit