fix: make Security Analysis workflow resilient to MCR pull failures#27
Merged
idvoretskyi merged 1 commit intomainfrom Apr 27, 2026
Merged
fix: make Security Analysis workflow resilient to MCR pull failures#27idvoretskyi merged 1 commit intomainfrom
idvoretskyi merged 1 commit intomainfrom
Conversation
Agent-Logs-Url: https://github.com/idvoretskyi/dev/sessions/207c0d3b-b9bf-4e7d-82ee-ce65ecdb1de6 Co-authored-by: idvoretskyi <118459+idvoretskyi@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
idvoretskyi
April 27, 2026 12:57
View session
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.
The
Security Analysisworkflow was failing entirely whenmcr.microsoft.comreturned403 Forbiddenpulling the devcontainer base image — no SARIF files were produced, causing Trivy and CodeQL upload steps to error out.Changes
id: build+continue-on-error: trueso a transient MCR outage no longer fails the jobif: steps.build.outcome == 'success'so they skip cleanly rather than crash when the image isn't availableCRITICAL,HIGH; no change needed