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
Should ignore publishing registries repositories #17067
Comments
reproduced, we are parsing it as part of our registry urls
|
Forked to https://github.com/renovate-reproductions/17067 Does it look like a quick fix, or needs some of our parsing rewritten? |
we use tokenizer , i have no idea, the code is here i suppose: renovate/lib/modules/manager/gradle/parser.ts Lines 281 to 313 in e4dbd4a
|
@zharinov do you recall if it's just checking for |
the tokenizer is matching specific keywords for multiple cases,
the customer input is:
in code, only case 7 could have caught this. here it is: renovate/lib/modules/manager/gradle/parser.ts Lines 719 to 730 in ca15793
|
@PhilipAbed thanks for the analysis. Let's hand over to @zharinov |
🎉 This issue has been resolved in version 34.32.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
How are you running Renovate?
Mend Renovate hosted app on github.com
If you're self-hosting Renovate, tell us what version of Renovate you run.
No response
Please select which platform you are using if self-hosting.
No response
If you're self-hosting Renovate, tell us what version of the platform you run.
No response
Was this something which used to work for you, and then stopped?
I never saw this working
Describe the bug
The bot uses registry urls from publishing config when trying to find updated dependencies. This is a config that is only used when publishing artifacts and is not supposed to be used when resolving dependencies.
An example of a config can look like this in a gradle file eg.
build.gradle.kts
Example repository: https://github.com/JohNan/renovatebot-bugreport
Relevant debug logs
Logs
Have you created a minimal reproduction repository?
I have linked to a minimal reproduction repository in the bug description
The text was updated successfully, but these errors were encountered: