Skip to content

ci: group major dependabot bumps per ecosystem #388

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

Merged
Aureliolo merged 1 commit into from
Mar 14, 2026
Merged

ci: group major dependabot bumps per ecosystem #388

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions .github/dependabot.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ updates:
groups:
minor-and-patch:
update-types: [minor, patch]
major:
update-types: [major]
open-pull-requests-limit: 10
reviewers:
- Aureliolo
Expand All @@ -29,6 +31,8 @@ updates:
groups:
minor-and-patch:
update-types: [minor, patch]
major:
update-types: [major]
open-pull-requests-limit: 10
reviewers:
- Aureliolo
Expand All @@ -46,6 +50,8 @@ updates:
groups:
minor-and-patch:
update-types: [minor, patch]
major:
update-types: [major]
open-pull-requests-limit: 5
reviewers:
- Aureliolo
Expand All @@ -65,6 +71,8 @@ updates:
groups:
minor-and-patch:
update-types: [minor, patch]
major:
update-types: [major]
Comment on lines +74 to +75
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot Mar 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While grouping all major updates will solve the problem of interdependent packages, it might create large and hard-to-review pull requests by bundling unrelated major version bumps. This could make it difficult to roll back a specific update if it causes issues.

A more targeted approach would be to use pattern-based grouping only for the packages that are known to be interdependent. This would solve the issue you described with echarts and vue-echarts without affecting other major updates.

For example, you could configure it like this:

      echarts-stack:
        patterns:
          - "echarts"
          - "vue-echarts"
        update-types:
          - "major"

open-pull-requests-limit: 10
reviewers:
- Aureliolo
Expand All @@ -82,6 +90,8 @@ updates:
groups:
minor-and-patch:
update-types: [minor, patch]
major:
update-types: [major]
open-pull-requests-limit: 5
reviewers:
- Aureliolo
Expand All @@ -96,6 +106,11 @@ updates:
timezone: Etc/UTC
commit-message:
prefix: "chore"
groups:
minor-and-patch:
update-types: [minor, patch]
major:
update-types: [major]
open-pull-requests-limit: 5
reviewers:
- Aureliolo
Expand All @@ -110,6 +125,11 @@ updates:
timezone: Etc/UTC
commit-message:
prefix: "chore"
groups:
minor-and-patch:
update-types: [minor, patch]
major:
update-types: [major]
open-pull-requests-limit: 5
reviewers:
- Aureliolo
Expand All @@ -124,6 +144,11 @@ updates:
timezone: Etc/UTC
commit-message:
prefix: "chore"
groups:
minor-and-patch:
update-types: [minor, patch]
major:
update-types: [major]
open-pull-requests-limit: 5
reviewers:
- Aureliolo
Expand Down
Loading