How do matchers work if groups are overlapping?

[ulgens]

How are you running Renovate?

A Mend.io-hosted app

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

42.19.9

Please tell us more about your question or problem

In this repo, I have the following dependency structure:

• CI dependencies: https://github.com/ulgens/django-blasphemy/blob/d03281653f65088830b8836535e54e2e0c9d9dd9/renovate.json5#L56
• Docker dependencies: https://github.com/ulgens/django-blasphemy/blob/main/renovate.json5#L63
• pre-commit dependencies https://github.com/ulgens/django-blasphemy/blob/d03281653f65088830b8836535e54e2e0c9d9dd9/renovate.json5#L70
• python dependencies: https://github.com/ulgens/django-blasphemy/blob/main/renovate.json5#L77

These four groups are defined by group / category names and they are working fine. I also have the following packages and I install them from separete categories/managers:

• Python - included in Docker dependencies and custom
• Ruff - included in CI, pre-commit and Python dependencies
• uv - included in Docker dependencies and custom
• prek - included in Docker - Python dependencies and custom

With the 4 groups I listed in the first part, when there is an update for one of these packages, renovate creates multiple PRs. For example, uv 0.9.14 update:

• chore(deps): update dependency uv to v0.9.14 ulgens/django-blasphemy#829 - custom
• chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.9.14 ulgens/django-blasphemy#830 - Docker group

I want to create new groups for these 4 dependencies, so when there is an update for one of them, I'll have only 1 PR to handle.

I tried to configure this behaviour at https://github.com/ulgens/django-blasphemy/blob/d03281653f65088830b8836535e54e2e0c9d9dd9/renovate.json5#L84 but renovate is still creating multiople PRs for each dependency. This is the result after adding the new groups:

 - [ ] <!-- unschedule-branch=renovate/ruff -->chore(deps): update dependency ruff to v0.14.7
 - [ ] <!-- unschedule-branch=renovate/uv -->chore(deps): update dependency uv to v0.9.14
 - [ ] <!-- unschedule-branch=renovate/docker-dependencies -->chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.9.14
 - [ ] <!-- unschedule-branch=renovate/pre-commit-dependencies -->chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.14.7

I tried to add the package name-based groups at the top first, and it didn't work. Then I moved them to the end of the list in the config file, hoping the last ones would have priority, but it didn't work either.

https://docs.renovatebot.com/configuration-options/#packagerules mentions that

The order of rules matters, because later rules may override configuration options from earlier ones, if they both specify the same option.

but it doesn't seem to be case here.

Not sure what I should do to give priority to package name based groups.

Logs (if relevant)

Logs

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

[RahulGautamSingh]

Last one will override the ones before it.

[ulgens]

But it doesn't work in my case, as I explained above.

[RahulGautamSingh]

You are using exact pkg names ie. ruff or uv instead convert those to regex / blob...then if the uv or ruff string are found in the pkg name then they'' be grouped together.

[ulgens]

I'm missing why you think exact matches are not valid.

Use this field to match against the packageName field. This matching can be an exact match, Glob match, or Regular Expression match.

https://docs.renovatebot.com/configuration-options/#matchpackagenames

The doc clearly states that an exact match should work, and then gives an example using an exact match.

[RahulGautamSingh]

It's not invalid, but also not suitable for your case.

uv will match uv but not ghcr/io/astral-sh/uv as you are expecting. For that, you'd need a regex/glob pattern.

You can try ChatGPT for more clarification

[ulgens]

I see. Not sure why but I thought ghcr.io/astral-sh/uv was also recognized as uv. After updating the config with the correct names, it's working fine. Thank you.