Repository navigation
Adopt r0 image revisions - #8
Merged
Merged
Conversation
Select published image revisions and advance chart and inherited-service references together.
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.
This service remains pinned to base revisions that select legacy images. Advance the base-service references and any local image options so the resolved service uses published r0 image revisions.
Image tags:
8.2-r0,8.3-r0,8.4-r0,8.5-r0.Planned service release:
1.3.8(current latest tag:1.3.7).Release dependencies:
3.0.0before releasing this service.Validation: 6 service-option combinations rendered against the proposed charts; workload selectors, container names, and image values matched. Every selected image revision was checked against its published registry digest and annotated Git alias. Manifest schema comparison found no new errors.
The Drupal manifests retain an existing schema finding for
actions[].privileged; this image migration leaves that field unchanged. Full server-side import validation was not run.