feat!: categories

[secustor]

Changes

This PR adds categories to managers and implements a matcher for package rules.

Context

• closes Replace programming language with categories #13953

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

https://github.com/secustor/renovate_autodiscoverfilter

[rarkins]

What are your thoughts on whether to remove languages in favour of categories?

[secustor]

What are your thoughts on whether to remove languages in favor of categories?

I think we should remove it as it basically does the same, but is more flexible. If we want to group tags together we could replace tags with labels ( key/value pairs) and allow matches to them.

e.g:
language:jvm to match specifically managers with a language=jvm label
language:* / language:/.+/ match all managers which have a language tag

use-case: deactivate all activity of Renovate except renovating actual source code

{
  "packageRules": [
    {
       "matchCategories": ["language:!/.+/"],
       "enabled": "false"
    }
  ]
}

That way we can prevent name collisions and give the user more match options.

From a migration standpoint the steps would be as following:

1. merge this PR
2. Replace languages with categories in the docs and website
3. Add waning to the DependencyIssue and PRs if matchLanguages is used
4. After some time remove the language in a breaking release

[rarkins]

packageRules using matchCategories can only be applied after extraction? e.g. you cannot use categories to change how the extraction config itself looks?

[secustor]

packageRules using matchCategories can only be applied after extraction? e.g. you cannot use categories to change how the extraction config itself looks?

No, I haven't been aware of this. So this is also the case currently for matchLanguages, which I have modeled matchCategories after?

[rarkins]

Thoughts on removing languages/matchLanguages at the same time? I think we could migrate it reasonably successfully.

[secustor]

I think we should implement in parallel at first and deprecate language settings as we try to reduce migration code.

From a technical standpoint there is no reason which would prevent this, but we have changes which does not map one to one.
Such a case is the docker category which is not applied the same as the docker programming language https://github.com/renovatebot/renovate/pull/16534/files#diff-3a57948c086543a7aaafd693e336ed8b566d6a93804fab7d7f2f27af39aaadddR5

[HonkingGoose]

I'm happy with the Markdown docs.

I'll let the maintainers review the code. 😉

[rarkins]

Any preview of how the autogenerated docs will look?

[viceice]

readded comment

[HonkingGoose]

I've read the changed docs, but I don't know if the changes are good or bad.

[rarkins]

I think this is the coverage analysis for this PR: https://app.codecov.io/gh/renovatebot/renovate/pull/16534

[viceice]

otherwise LGTM

The merge-base changed after approval.