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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this cleanup loop, adding
--asyncmeans the workflow exits after each delete operation is submitted rather than after Artifact Registry reports that it completed; the gcloud reference for this flag says it returns immediately without waiting for the operation. When Artifact Registry later rejects a delete (for example a digest that fails a precondition or another backend-side delete error), this step still finishes green, so old Cloud Run images remain in the repository and cleanup regressions are hidden from CI. Please either wait on the returned operations or keep the synchronous delete so failures still fail the workflow.Useful? React with 👍 / 👎.