fix(presets): Revert "fix(presets): actually group Node.js packages"

[rarkins]

Reverts #34244

[rarkins]

@maxbrunet the original change causes an undesirable change of branch name

e.g. I saw a change from rarkins/nvm6#5 to rarkins/nvm6#7 in one of my test directories. Branch name changed from renovate/node-20.x to renovate/node.js

[maxbrunet]

Yes, like the other groups, why is it undesirable?

[rarkins]

Because it's lost the major version part

[maxbrunet]

So if we set branchTopic on this preset, that'd be acceptable?

"branchTopic": "node-{{{newMajor}}}{{#if separateMinorPatch}}{{#if isPatch}}.{{{newMinor}}}{{/if}}{{/if}}.x"

[rarkins]

Why does it need to be a group name if it's all the same depName?

[maxbrunet]

It's not all the same depName, the package can have the Docker registry as prefix: /(?:^|/)node$/

[rarkins]

That can remain as packageName

[maxbrunet]

hmm not sure what do you mean, let's say we have that (for all of these depName==packageName):

# Dockerfile
FROM node:22.14.0
FROM library/node:22.14.0
FROM docker.io/library/node:22.14.0
FROM public.ecr.aws/docker/library/node:22.14.0

And a .nvmrc

22.14.0

How would Renovate be able to group them?

[rarkins]

Yes if depName is "Node.js" for all

[renovate-release]

🎉 This PR is included in version 39.177.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 39.177.0

Your semantic-release bot 📦🚀