Support replacement PRs on all managers

[HonkingGoose]

What would you like Renovate to be able to do?

Right now we only raise replacement PRs for npm dependencies.

I think we want to support all managers eventually.
This is a big issue to track support for all managers:

• bazel
• git-submodules
• gomod
• gradle
• hermit
• homebrew
• maven
• regex
• sbt

Existing issues:

• Replacing deprecated dependencies for docker datasource only replace version #12623
• Replacement PR body text confusion if repo has custom rules #12625
• Replacement PRs are only implemented for npm right now #12626
• feat: autoreplace support for replacements #13211

Once we support all managers, we should update the readme.md in this repository, and the src/index.md file in the docs repository. Both have a sentence that mentions this issue (#14149).

If you have any ideas on how this should be implemented, please tell us here.

Nope.

Is this a feature you are interested in implementing yourself?

No

[JamieMagee]

#13211 will cover ~75% of managers. I need to get back on that PR

[hoerup]

Would it be possible to expand this logic with a "replace to none" / "remove"

[JamieMagee]

Would it be possible to expand this logic with a "replace to none" / "remove"

Maybe? But not with the current set of changes that are in PR right now

[JamieMagee]

Closed:

• feat: autoreplace support for replacements #13211
• feat: replacement support for more autoreplace managers #17476

In progress:

• feat(replacement): datasource changes #17881
• fix: replacement for pep440 versioning #17882
• feat: replacement support for all managers #17883

[JamieMagee]

I've updated the list in the issue body to reflect the currently supported managers.

[MPV]

Could we also add sbt in the issue body as a manger not yet supported?

It's tracked in:

• Support autoreplace for sbt manager #25643

[HonkingGoose]

@rarkins you moved this issue to a discussion, but we still link to the old issue (#14149) on the:

• Docs homepage
• Main repository readme.md

What do you want me to do?

1. Update links on docs homepage and readme.md to point to this discussion
2. Drop the reference completely

   Get replacement PRs to migrate from a deprecated dependency to the community suggested replacement, works with most managers, see issue 14149 for exceptions

3. Copy information from discussion into a Renovate docs page (maybe Renovate docs, Replacement Presets, and link to that
4. Something else

[HonkingGoose]

@rarkins I hope it's okay to poke you after about three months. 🙃 We're still referring to the previous issue, and this discussion is not resolved yet. So there's still things we need to do.

Can you decide what to do?

[TWiStErRob]

What would be required to get Maven replacements?
This would cover Java/Kotlin/Android/Groovy/Maven/Gradle/Bazel ecosystems.

---

Note: https://jakewharton.com/java-interoperability-policy-for-major-version-updates/ which suggests that relocations should happen on every major release, and it is happening on some.

[rarkins]

Support needs to be added to updateDependency() for each manager. Any which doesn't have its own updateDependency() function shouldn't need any changes and already work

[lyonlai]

👋 for Hermit manager, although it has anupdateDependency method, it doesn't seem to impact the replacement PR functionalities.

I have used and tested the replacementName and replacementVersion very early days right after I developed this manager. Mainly to replace dependencies managed by Hermit channel to specific version so that Renovate takes over the update in the future.

A recent issue brought this page into my attention. hermit is marked as not supporting replacement PRs that guides our engineers to have gone down to an alternative path where replacement PR could apply. I have spent some time digging into the source and retried this replacement functionality with hermit manager and found it works as expected.

To avoid future confusion, I would like to tick the box for the hermit manager here. Would you mind me send a PR to update the doc?

If there's anything missing please let me know.

[lyonlai]

Turn out I made a mistake in the previous statement. Only replacementVersion works and there changes are required in Hermit manager to have make replacementName works. I've added a PR for it. Please take a look.

[jamietanna]

I've made a stab at the support for gomod in #29575

[dsegurag]

Hi!

I want to expose my case.

I have a private GitLab instance deployed and I need to catch the tags of one repo. In order to do that, I'm using a customManagers like:

"customManagers": [
  {
    "customType": "regex",
    "fileMatch": "Makefile",
    "matchStrings": ["PACKAGE_VERSION\\s:=\\s(?<currentValue>\\d+\\.\\d+.\\d+)"],
    "registryUrlTemplate": "https://gitlab.example.com",
    "depNameTemplate": "59064",
    "datasourceTemplate": "gitlab-tags",
    "versioningTemplate": "semver"
  }
]

The problem I see here is that the depNameTemplate property has the internal ID of the project I want to grab the tags and as a result, the dependency name it's 59064 which is not really nice...

Seems that having the replacementName property available for regex would be nice in my case.

Happy to hear any other way to achieve it.

Thanks all!