Group updates across different ecosystems #8126
Labels
F: grouped-updates 🎳
Relates to bumping more than one dependency in a single PR
Keep
Exempt this from being marked by stalebot
T: feature-request
Requests for new features
Comments
jakecoffman
added
the
F: grouped-updates 🎳
|
Thanks for raising this; the crew is starting to explore this. Tagging @honeyankit and @Nishnha |
7 tasks
|
This would be very useful. I have projects with multiple package ecosystem definitions per Maven POM and can't group them right now since #2178 isn't implemented. |
|
This would be brilliant for us |
1 task
jim
pushed a commit
to chicago-tool-library/circulate
that referenced
this issue
Mar 18, 2024
# What it does Reconfigure dependabot to run weekly instead of daily, and have it batch updates into a few groups. # Why it is important Dependabot has proven to be moderately noisy when running daily, so I think it's worth trying to see if batching feels easier to manage. # Implementation notes * There are a lot of tools for deciding what gets batched together. As I start I tried splitting out rails and linter updates from others, but it'll be easy to tweak these as we learn more. * Notably [dependabot cannot batch updates across package ecosystems yet](dependabot/dependabot-core#8126), so rails upgrades will still likely need to be done manually so we sync the npm and ruby packages. # Your bandwidth for additional changes to this PR _Please choose one of the following to help the project maintainers provide the appropriate level of support:_ - [x] I have the time and interest to make additional changes to this PR based on feedback.
|
We have a private repo that publishes both a ruby gem and npm package, and would greatly benefit from grouping these together in dependabot PRs for other consuming repos, so that both can be updated at once. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Feature description
If I have a project using several
package-ecosystemconfigurations, I would like to use the newgroupsfeature to create a Dependabot PR that includes updates across multiple ecosystems. For example, I may be using Dependabot for docker, terraform, and pip. Currently, I have three separate groups, one for each eco-system, and so I get three separate PRs. Instead, I would like to get a single PR.The text was updated successfully, but these errors were encountered: