Reduce log levels for registry connection checks - #3516
Merged
mbg merged 2 commits intoFeb 26, 2026
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request reduces the log levels for private registry connection check messages in the start-proxy action to minimize workflow annotation noise. Connection test failures that previously logged as errors now log as info or warning, making the logs less noisy for non-critical diagnostic checks.
Changes:
- Changed HTTP status code failures (e.g., 400, 404) from error to info level
- Changed network errors and timeouts from error to warning level
- Changed top-level exception handler from error to warning level
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/start-proxy/reachability.ts | Reduced log levels for connection check failures from error to info/warning |
| lib/start-proxy-action.js | Generated JavaScript code (mirrors TypeScript changes) |
Sorry, something went wrong.
sam-robson
approved these changes
Feb 26, 2026
This was referenced Feb 27, 2026
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.
Reduces the log levels of the connection check messages, to reduce noise from workflow annotations
Note: liner failures are unrelated to this PR and will be resolved by #3512
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types:
Products:
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist