dependabot / dependabot/dependabot-core

Add Support for Separate Pull Requests for Major, Minor, and Patch Version Updates

Open
#6,957 8 comments 37 reactions 0 assignees View on GitHub
T: feature-request
Dominant language
Ruby
Stars
5.8k
Forks
1.5k
Avg merge
2d 18h
Merged PRs (30d)
149

Description

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Feature description

Currently, Dependabot does not provide a native way to separate Pull Requests for major, minor, and patch version updates within the same configuration. As a result, users cannot easily distinguish between different update types and may unintentionally merge major version updates that require more extensive testing and refactoring.

**Feature Request:**

I propose the addition of a feature that allows Dependabot to create separate Pull Requests for major, minor, and patch version updates. This would enable users to better manage updates by having dedicated Pull Requests for each update type, making it easier to prioritize and review changes based on their potential impact.

**Example:**

```
version: 2
updates:
- package-ecosystem: "npm"
directory: "/"
schedule:
interval: "weekly"
commit-message:
prefix: "Dependabot Minor/Patch"
versioning-strategy: "increase"
update-types: ["version-update:semver-minor", "version-update:semver-patch"]

- package-ecosystem: "npm"
directory: "/"
schedule:
interval: "weekly"
commit-message:
prefix: "Dependabot Major"
versioning-strategy: "increase"
update-types: ["version-update:semver-major"]
```

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by tracing how Dependabot reads update-types and groups updates using the npm example configuration; done means users can configure separate major, minor, and patch pull requests without unintended mixing.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, ruby
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.