Repository navigation
Conversation
addshore
force-pushed
the
ci-skip-unchanged-image-prs
branch
from
October 16, 2026 23:47
0942985 to
dda7d6f
Compare
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.
Compose-only changes can currently generate deployment PRs even when the runnable image does not need to change. Compare the new linux/amd64 image manifest digest with each environment's configured image, and update values and create deployment PRs only where the digests differ.
This should be considered in combination with either #1301 or #1302
These tackle not introducing file changes that are not needed into the images
And this PR then tackles comparing generated images at an appropriate level.
Move generated revision/version/time metadata from image labels to index annotations so it remains available without changing the runnable image. Keep SHA tags and provenance. Comparison failures stop the job; staging/local and production are checked independently.
(As far as I can see the labels themselves are not directly used in this repo or the deploy repo?)
Real local Docker builds with the either allowlist .dockerignore reproduced the exact Compose change from 7294d3d: index digests differed, platform digests matched
I also appreciate if / as the team moves towards other auto deploy methods, this might not be wanted, however it could be a useful little increment for now?
(Not sure how often those generated PRs end up needing to be closed)