Please check if your PR fulfills the following requirements:
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] Build (npm run build) was run locally and any changes were pushed
[ ] Tests (npm test) were run locally and passed
[x] Prettier (npm run prettier) was run locally and passed
Pull request type
Please check the type of change your PR introduces:
- [ ] Bugfix
- [ ] Feature
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] Documentation content changes
- [x] Other (please describe): Renovate changes
## What is the current behavior?
With the Rollup v4 release, we got a handful of PRs for rollup package bumps. It'd be nice if we just got 1
GitHub Issue Number: N/A
What is the new behavior?
add a groupName to the rollup dependencies to see if that properly creates PRs
Does this introduce a breaking change?
[ ] Yes
[x] No
Testing
Ran renovate-config-validator, but we won't know for sure until this lands
Pull request checklist
Please check if your PR fulfills the following requirements:
npm run build) was run locally and any changes were pushednpm test) were run locally and passednpm run prettier) was run locally and passedPull request type
Please check the type of change your PR introduces: - [ ] Bugfix - [ ] Feature - [ ] Refactoring (no functional changes, no api changes) - [ ] Build related changes - [ ] Documentation content changes - [x] Other (please describe): Renovate changes ## What is the current behavior?With the Rollup v4 release, we got a handful of PRs for rollup package bumps. It'd be nice if we just got 1
GitHub Issue Number: N/A
What is the new behavior?
add a groupName to the rollup dependencies to see if that properly creates PRs
Does this introduce a breaking change?
Testing
Ran
renovate-config-validator, but we won't know for sure until this landsOther information