fix(galaxy-collection): suppress incorrect warning if collection is not found in registry#36697
Merged
rarkins merged 2 commits intorenovatebot:mainfrom Jun 26, 2025
dmosen:fix/incorrect_warning_if_collection_not_found
Merged
fix(galaxy-collection): suppress incorrect warning if collection is not found in registry#36697rarkins merged 2 commits intorenovatebot:mainfrom dmosen:fix/incorrect_warning_if_collection_not_found
rarkins merged 2 commits intorenovatebot:mainfrom
dmosen:fix/incorrect_warning_if_collection_not_found
Conversation
RahulGautamSingh
approved these changes
Jun 26, 2025
rarkins
approved these changes
Jun 26, 2025
|
🎉 This PR is included in version 41.12.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
Changes
Prevent logging of warnings if a collection is not found in a registry
Context
If a collection is not found in one or more of the defined galaxy-collection registries, a warning is logged. This shows up in the logs and in the Dependency Dashboard. This is misleading and should be considered normal behavior.
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: