chore(dependabot): drop separate 'monthly' block for updating some npm deps #292
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…m deps Today I noticed a new check failure on the latest commit to main. It was to dependabot.yml. The failure: > Your .github/dependabot.yml contained invalid details > Update configs must have a unique combination of 'package-ecosystem', 'directory', and 'target-branch'. Ecosystem 'npm' has overlapping directories. I don't know if this is a new constraint or was just not noticed before. I am hoping dropping the 'monthly' block here will suffice. We will just deal with aws-sdk updates weekly, distracting though that will be.
|
Link to the workflow run with the failure: |
david-luna
approved these changes
Jul 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Today I noticed a new check failure on the latest commit to main. It was to
dependabot.yml. The failure:
I don't know if this is a new constraint or was just not noticed before.
I am hoping dropping the 'monthly' block here will suffice. We will
just deal with aws-sdk updates weekly, distracting though that will be.