Repository navigation
chore: release patched backend services as 1.0.2 - #272
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Docker Publish correctly refused to move an existing backend-admin:v1.0.1 tag to a different digest after the dependency and Boot4 compatibility repairs. Allocate a new patch release instead of changing the immutable-tag guard.
Set all seven backend service release properties to1.0.2 in both the root and owner POMs, align the existing supply-chain/promotion test fixtures, and document the version/digest rule in OPERATIONS. Frontend source tags, shared parent revision2.0.0, runtime business code, scanning/signing gates and the promoter are unchanged.
Validation atf94c89f63167749530e078f8546a7e1f26e8d7e0: specification, standards and Java reviews approved; whitespace checks passed. The remote full supply-chain contract completed with persisted exit0, covering version consistency, digest-only candidates, pinned Actions, promotion negative/dry-run/idempotency/partial-failure cases, evidence and deploy policy. This fake-Docker test did not publish artifacts. Remote Docker registry preflight returned canonical not-found for all seven v1.0.2 tags; it is not a reservation. Actual publication still checks every planned tag and refuses conflicting digests. Fresh candidate CI, graph update and actual publication are pending. No production deployment is claimed.