Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support replacement PRs on all managers #14149

Closed
3 of 12 tasks
HonkingGoose opened this issue Feb 10, 2022 · 6 comments
Closed
3 of 12 tasks

Support replacement PRs on all managers #14149

HonkingGoose opened this issue Feb 10, 2022 · 6 comments
Labels
priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)

Comments

@HonkingGoose
Copy link
Collaborator

HonkingGoose commented Feb 10, 2022 •
edited
Loading

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

Existing issues:

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
@HonkingGoose HonkingGoose added type:feature Feature (new functionality) status:requirements Full requirements are not yet known, so implementation should not be started priority-5-triage labels Feb 10, 2022
@HonkingGoose HonkingGoose mentioned this issue Feb 10, 2022
Closed
@viceice

This comment was marked as resolved.

Sign in to view
@JamieMagee
Copy link
Contributor

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

@HonkingGoose HonkingGoose added priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others and removed priority-5-triage labels May 31, 2022
@hoerup
Copy link

hoerup commented Sep 29, 2022

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

@JamieMagee
Copy link
Contributor

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
Copy link
Contributor

Closed:

In progress:

@t-kulmburg t-kulmburg mentioned this issue Dec 1, 2022
Merged
@JamieMagee
Copy link
Contributor

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

@HonkingGoose HonkingGoose mentioned this issue Sep 7, 2023
Merged
6 tasks
@renovatebot renovatebot locked and limited conversation to collaborators Oct 1, 2023
@rarkins rarkins converted this issue into discussion #24883 Oct 1, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@hoerup @JamieMagee @viceice @HonkingGoose and others