refactor: increase the limit of PRs being opened by dependabot in parallel #51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
source: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#open-pull-requests-limit
currently dependabot doesn't open any new PRs if the amount of open PRs by dependabot (currently 5) is even already reached. Especially within the Elements repo we might have some more PRs open, especially regarding major framework updates (and dependabot even also doesn't support grouping related dependencies so far, so the problem might even further increase), which would lead to that dependabot silently skips until the next cycle to analyse for new updates.
We might even also be able to deactivate this limit in total, but I still like the idea to at least limit it to around 10 or so, and work with a daily check for new updates.
similar to db-ui/base#49 and db-ui/elements#247