chore(ci): update Dependabot groups for typedoc #2716
Merged
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.
Summary
Changes
This PR updates the Dependabot configuration to group together the
typedoc
module and its plugins so that the bot opens PRs for all the packages together.This is beneficial since the plugins usually support a specific version or range of
typedoc
, which means upgrading one without the others is not desirable.Typedoc updates usually come out together with new TypeScript "major" releases, so I could've added TS to the group as well, however I opted not to so that we have a discrete PR for TypeScript, given the large blast radius of a botched upgrade.
While touching the file, I also made two minor changes to other groups:
aws-sdk
group toaws-sdk-v3
so to not confuse it with PRs opened for theaws-sdk
(v2) dependency**
to*
. I made this change because I noticed that this CDK package was not being picked up, which is weird since the same glob pattern was working on the AWS SDK for JavaScript v3. After checking the Dependabot docs I couldn't find any example of**
so I changed to*
which is used extensively.Issue number: closes #2715
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.