matchPackagePrefixes no longer works?

[jycouet]

What would you like help with?

I would like help with my configuration

How are you running Renovate?

Mend Renovate hosted app on github.com

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

Since a few days, I have all deps update grouped into 1 PR (2 actually as one is major).
You can actually see it here: https://github.com/jycouet/kitql/pulls
I have a central config located here: https://github.com/jycouet/jycouet/blob/main/shared-config/renovate/default.json5

I'm using this matchPackagePrefixes and it looks like in v38 of renovate things have changed with this setting.
I don't find the link to see logs of the bot, maybe some deprecation are written somewhere?
Maybe deprecation could be listed in the 📦 Dependency Dashboard issue

I maybe missed something?
Thank you for your help

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

Good luck,

The Renovate team

[rarkins]

Please create a minimal reproduction. MatchPackagePrefixes was removed in v38 and in the release notes but they should be automatically migrated.

[RahulGautamSingh]

I meant migrating internally.

I have opened a discussion on our slack regarding your request, will create an issue when we reach a conclusion.

[RahulGautamSingh]

@jycouet You can check this discussion. Here the author has setup config validation for their default.json. Maybe you can setup something similar in your renovate-config repo. It won't lead to creation of migration PRs but you will still get warnings in logs, when the config needs migration.

[jycouet]

Interesting, I didn't know about this config. I'm also not running renovate myself, it's the bot running it. So I'm not sure it's applying to me.

[RahulGautamSingh]

Repro: https://github.com/Rahul-renovate-testing/repro-30891 We can fix this my migrating, but then should we do the same for all other matchers & excluders which we deprecated as they are similar. eg. matchDepPrefixes

#31083

[jycouet]

Close to this issue, I got this issue on RenovateMe: jycouet/VSTSExtensions#78 (comment)
Could it be that the config has also an obsolete key?
(On RenovateMe, there is not creation of issue in DevOps)

[rarkins]

How is that related to this issue?

[jycouet]

It's just a guess, I could be wrong.
What gave me the hint is that both are using latest renovate and both stopped working on the same day!

In my case: A
=> My config is in another repo, and I never got an issue: Action Required: Fix Renovate Configuration. So my config is wrong and I don't know about it.

In his case: B
=> He is using RenovateMe so on microsoft stuff. And there, issue creation is not supported. So maybe his config is wrong and he doesn't know about it.

So, my guess is that on july 21, the new release didn't pick up some old config style.

[jycouet]

Wrong hint!
It was a node configuration issue in case B.

For case A (mine), I updated my config to match nowdays config style and it's working as expected. 😊