Skip to content
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.

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

chore: Use Dependabot groups to bundle PRs #555

Merged
merged 1 commit into from May 12, 2024
Merged

chore: Use Dependabot groups to bundle PRs #555

merged 1 commit into from May 12, 2024

Conversation

nschonni
Copy link
Member

@nschonni nschonni commented May 8, 2024

Potentially this could just be one big blob of updates of prod+dev, but I thought splitting it might make sense. This way, the next time there is a ton of remark-lint bumps, we'll only get one PR.
I flipped the cadence for NPM PRs to weekly, since I don't know if there is a need for daily PRs, even with the bundled updates.

@Trott
Copy link
Member

Trott commented May 10, 2024

I'm not opposed to this, but it is worth mentioning that the last time we had a bunch of remark-lint-* updates, there were two or three that couldn't land, so there was arguably benefit to getting them one at a time so you could readily identify which ones were failing and land all the other ones before troubleshooting the ones with breaking changes.

That said, this won't make identifying issues impossible or anything like that, and the convenience for the happy path/typical case might be worth the small cost when there's a problem.

@nschonni nschonni merged commit c8c3679 into main May 12, 2024
6 checks passed
@nschonni nschonni deleted the dep-groups branch May 12, 2024 20:29
@nschonni
Copy link
Member Author

@Trott I have similar concerts about tracing down what's broken too. I've landed it to give it a try, but if it doesn't work out, we can easily revert it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants