Skip to content
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.

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

[Feature Request] Increase simultaneous dependabot version bumps #17564

Open
dbwiddis opened this issue Mar 10, 2025 · 0 comments
Open

[Feature Request] Increase simultaneous dependabot version bumps #17564

dbwiddis opened this issue Mar 10, 2025 · 0 comments
Labels
enhancement Enhancement or improvement to existing feature or request Libraries Lucene Upgrades and Libraries, Any 3rd party library that Core depends on, ex: nebula; team is respo untriaged

Comments

@dbwiddis
Copy link
Member

dbwiddis commented Mar 10, 2025

Is your feature request related to a problem? Please describe

Dependabot is currently configured to have only one open version bump PR per module, with weekly updates. For example, here is the configuration for repository-azure

- directory: /plugins/repository-azure/
open-pull-requests-limit: 1
package-ecosystem: gradle
schedule:
interval: weekly

While this appears intended to reduce PR spam from version bumps, it has an unfortunate side effect. When a version bump is stalled for some reason, no other version bumps go through. See for example:

This is significant because the version of a completely different dependency was never bumped, despite being needed to resolve CVE-2024-57699, published Feb 5 (33 days ago).

Describe the solution you'd like

Increase the limit of open PRs to 2, to prevent a single stalled version bump from blocking all others for a module.

Related component

Libraries

Describe alternatives you've considered

  • Change dependency management to Mend Remediate. While the same PR throttling limits (and more flexibility) is included, it provides a "Dependency Dashboard" where one can also view pending PRs which have been throttled, and click a box to request a PR; a good workflow to establish in the run-up to a release when fixing CVEs should be a priority.
  • Investigate any other way to prioritize CVE-fixing version bumps

Additional context

No response

@dbwiddis dbwiddis added enhancement Enhancement or improvement to existing feature or request untriaged labels Mar 10, 2025
@github-actions github-actions bot added the Libraries Lucene Upgrades and Libraries, Any 3rd party library that Core depends on, ex: nebula; team is respo label Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement or improvement to existing feature or request Libraries Lucene Upgrades and Libraries, Any 3rd party library that Core depends on, ex: nebula; team is respo untriaged
Projects
None yet
Development

No branches or pull requests

1 participant