Disable separateMajorMinor for pulldown-cmark dependency group
Finally figured it out, this was the issue that was preventing renovate from grouping pulldown-cmark and pulldown-cmark-to-cmark together in a single PR. See code comment for a more detailed description of why this is needed.
This commit is contained in:
parent
5bede0a357
commit
2bee08477d
10
.github/renovate.json5
vendored
10
.github/renovate.json5
vendored
@ -47,7 +47,15 @@
|
|||||||
// lockstep in case of breaking changes, so it's best to group them
|
// lockstep in case of breaking changes, so it's best to group them
|
||||||
// together.
|
// together.
|
||||||
"matchPackageNames": ["pulldown-cmark*"],
|
"matchPackageNames": ["pulldown-cmark*"],
|
||||||
"groupName": "pulldown-cmark (grouped)"
|
// pulldown-cmark is currently on a 0.x release series while
|
||||||
|
// pulldown-cmark-to-cmark tends to bump the major version
|
||||||
|
// component whenever pulldown-cmark creates a new release (which
|
||||||
|
// increments the minor component). Renovate by default creates
|
||||||
|
// separate PRs for major and minor bumps which fails to match up
|
||||||
|
// with the grouping. Disabling this behavior ensures that both
|
||||||
|
// packages are always updated together in a single PR.
|
||||||
|
"separateMajorMinor": false,
|
||||||
|
"groupName": "pulldown-cmark (group)"
|
||||||
},
|
},
|
||||||
],
|
],
|
||||||
ignorePaths: [
|
ignorePaths: [
|
||||||
|
Loading…
Reference in New Issue
Block a user