You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, the dependabot create individual PR for each dependency, after one get merged, all others have to be updated and go through all tests again, which brings longer waiting time for keep them up-to-date, worse case is some dependeded library not get updated in one batch, it may brings inconsistencies, for example. the k8s.io related libraries.
For this concern, actually dependabot configuration has introduced groups concept since 2023 which can group dependencies by naming patterns.
Now, in your dependabot.yml configuration file, you can set custom grouping rules for Dependabot based on pattern matching on package name. Here is an example of how these rules can be set up:
version: 2
updates:
- package-ecosystem: "bundler"
directory: "/"
schedule:
interval: weekly
# New!
groups:
# This is the name of your group, it will be used in PR titles and branch names
dev-dependencies:
# A pattern can be...
patterns:
- "rubocop" # a single dependency name
- "aws*" # or a wildcard string that matches multiple dependencies
# If you'd simply like to group as many dependencies together as possible,
# you can use the wildcard * - but keep in mind this may open a very large PR!
# Additionally, you can specify any dependencies to be excluded from the group
exclude-patterns:
- "aws-sdk"
This configuration applies to regularly scheduled Dependabot version updates only. Security updates for Dependabot will continue to open as individual pull requests, even if they match a configured grouping rule.
By default, the dependabot create individual PR for each dependency, after one get merged, all others have to be updated and go through all tests again, which brings longer waiting time for keep them up-to-date, worse case is some dependeded library not get updated in one batch, it may brings inconsistencies, for example. the k8s.io related libraries.
For this concern, actually dependabot configuration has introduced
groups
concept since 2023 which can group dependencies by naming patterns.Now, in your dependabot.yml configuration file, you can set custom grouping rules for Dependabot based on pattern matching on package name. Here is an example of how these rules can be set up:
This configuration applies to regularly scheduled Dependabot version updates only. Security updates for Dependabot will continue to open as individual pull requests, even if they match a configured grouping rule.
group candidates
Reference
https://github.blog/news-insights/product-news/a-faster-way-to-manage-version-updates-with-dependabot/
AC
The text was updated successfully, but these errors were encountered: