Is it possible to use version of one of dependencies for group version?

[osipxd]

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

I have several groups of Maven packages with BOM within, for example Firebase or Jetpack Compose. Usually, these packages release at the same time, but have different versions. I want to identify groups by version of BOM package. For example, I want to get firebase-bom 32.8.1 in the commit message containing all Firebase packages updates, but I'm getting only firebase-bom.
Here is my try to make it work using handlebars. If I understood it correctly, it is not possible to access upgrades in commitMessageExtra. So is my idea feasible?

{
  "description": "Group together all Firebase components",
  "matchPackagePrefixes": ["com.google.firebase"],
  "groupName": "firebase-bom",
  "group": {
    "commitMessageExtra": "{{#each upgrades as |upgrade|}}{{#if (equals upgrade.packageName 'com.google.firebase:firebase-bom')}}{{upgrade.newVersion}}{{/if}}{{/each}}"
  }
}

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.

To get started, please read our guide on creating a minimal reproduction.

Good luck,

The Renovate team

[rarkins]

Usually if you have a group of updates, and they all have the same version, then you'll see it in the PR title. Please create a reproduction to demonstrate your use case

[osipxd]

The problem is that firebase-bom contains dependencies with different versions. Here is a partial list of dependencies, for example:

The same for compose-bom. Some of the dependencies have different version and compose-bom itself uses different versioning strategy:

Here compose-bom version is 2024.04.01, most of the dependencies are 1.6.6 and meterial3 dependency is 1.2.1.

So I wonder if it is possible to use the version of a particular dependency to identify the whole group.

[rarkins]

I don't think there's any way to achieve this with current funtionality

[osipxd]

That's sad. Is there any chance upgrade will be supported in group configurations? Like in my example:

"group": {
  "commitMessageExtra": "{{#each upgrades as |upgrade|}}{{#if (equals upgrade.packageName 'com.google.firebase:firebase-bom')}}{{upgrade.newVersion}}{{/if}}{{/each}}"
}

[rarkins]

You're welcome to experiment to see if you can get it to work and submit a PR if an elegant solution is possible. As this is not a widely applicable feature or affecting a Mend.io customer then it's not something we would spend time on in the core team