New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(config): mergeable repositoryAliases
global option
#26848
Conversation
…default/manager option This should fix the repositoryAliases that are being defined in renovate.js or via the env var RENOVATE_REPOSITORY_ALIASES not actually being picked up as mentioned int he discussion renovatebot#26756
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.
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.
The change makes sense IMO.
I can not come up with a scenario in which we would break existing setups in which people use registryAliases.
@eschleining please don't merge main if not needed, you'll block automerge 🙃 |
Oh ok, thanks for letting me know. There are failing tests. Should I fix
them?
Michael Kriese ***@***.***> schrieb am Fr., 26. Jan. 2024,
21:13:
… @eschleining <https://github.com/eschleining> please don't merge main if
not needed, you'll block automerge 🙃
—
Reply to this email directly, view it on GitHub
<#26848 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGKE4OTOATCZC5LGCWL2M3YQQFAPAVCNFSM6AAAAABCJJ4YMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJSGYZTGMRVHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
yes |
Head branch was pushed to by a user without write access
689cb09
repositoryAliases
global option
🎉 This PR is included in version 37.158.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes
This should fix the repositoryAliases that are being defined in renovate.js or via the env var RENOVATE_REPOSITORY_ALIASES not actually being picked up as mentioned int he discussion.
Context
#26756
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: