feat(docker): tag ECR images with latest on release#188
Merged
debanjan97 merged 1 commit intomainfrom Apr 17, 2026
Merged
Conversation
Add a `latest` tag to ECR Docker image metadata steps so that release
builds produce both versioned and `latest` tags. The tag is gated behind
`enable=${{ github.event_name == 'release' }}` so PR and manual builds
are unaffected.
PRO-5596
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Scanned-by: gitleaks 8.29.0
Contributor
Docker Preview Images ReadyPreview Docker images have been built for this PR: ECR (internal): docker pull 422074288268.dkr.ecr.us-east-1.amazonaws.com/rudderstack/profiles-code-server:pr-188Image Details:
Test the image: docker run --rm -p 8080:8080 422074288268.dkr.ecr.us-east-1.amazonaws.com/rudderstack/profiles-code-server:pr-188
|
tipped73
approved these changes
Apr 17, 2026
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.
Why
CI pipelines that consume the code-server Docker image need to always pull the most recent release. Without a
latesttag, every pipeline must be updated with the exact version tag on each release. Tagging withlatestlets CI jobs use a stable reference that always points to the newest release.Summary
latesttag to the three ECR Docker metadata steps (docker meta,docker arm64 meta,docker amd64 meta) in thedocker-metadata-ecrjobgithub.event_name == 'release', so PR and manual dispatch builds are unaffecteddocker-manifest-ecrjob automatically creates a multi-archlatestmanifest from the arch-specificlatest-arm64andlatest-amd64tagsTest plan
pr-<N>tags (nolatest)v<VERSION>andlatesttagsdocker pull 422074288268.dkr.ecr.us-east-1.amazonaws.com/rudderstack/profiles-code-server:latestreturns the multi-arch imageResolves PRO-5596
🤖 Generated with Claude Code