-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Migrate deprecated internal presets #7572
Comments
The PR you shared only shows I don't think we need to explicity specify |
|
The bot uses the right
I don't really understand what this means, but I'll let you deal with this report how you see fit. 😄 😉 |
config:base-js
is deprecated, but Renovate onboarding PR uses deprecated config.
We don't have too many presets mentioned as deprecated: For each of these we should remove them and instead add a migration rule in https://github.com/renovatebot/renovate/blob/master/lib/config/migration.ts |
@rarkins maybe this issue can be moved from "needs requirements" to "ready" on the Renovate project board? Seeing as you already gave the "recipe" of the changes? |
We now don't have any presets with deprecated in their description |
What Renovate type, platform and version are you using?
GitHub hosted app.
Describe the bug
I'm confused about what the correct base configuration is...
The docs for config:base-js say this is deprecated:
But that's what the Renovate bot gives me with its on-boarding pull requests.
I noticed that there are separate configurations for web-apps and libraries:
Shouldn't the bot try to use either
config:js-app
orconfig:js-lib
in the on-boarding pull request?Relevant debug logs
To Reproduce
Take a look at this on-boarding pull request I got for a Docusaurus v2 web app: HonkingGoose/git-gosling@0cff589.The bot used the deprecatedconfig:base-js
template instead of theconfig:js-app
template.EDIT: Whoops! I totally misread the docs on this part, ignore the strike-through text.
Additional context
I think the Renovate bot already tries to determine if you have a web-app or library, to determine if it should pin your dependencies or not? So maybe this logic can be plugged into the onboarding pull request code?
The text was updated successfully, but these errors were encountered: