chore: add config for enabling Dependabot version updates #1347
There are no files selected for viewing
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| version: 2 | ||
| updates: | ||
| - package-ecosystem: gradle | ||
| directory: / | ||
| schedule: | ||
| interval: daily # means every _weekday_ (Monday through Friday) | ||
|
Contributor
There was a problem hiding this comment. It would be nice to also trigger it on a release of aws-crt-kotlin or aws-kotlin-repo-tools. I don't think that's possible with this yaml configuration though
Contributor
Author
There was a problem hiding this comment. The options for
Contributor
There was a problem hiding this comment. Yes I was thinking of a GitHub action that can trigger a Dependabot scan manually, there's a bit of discussion here: dependabot/dependabot-core#2980 |
||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the documentation I see:
which makes me think it should be pointing to
/gradle? But I also see this:which I think means Dependabot would automatically upgrade our GitHub action dependencies.
Do we need both?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so. Technically, the package manifest for Gradle starts from /settings.gradle.kt (if it exists) and /build.gradle.kts. It typically spiders out from there and may include /gradle/libs.versions.toml but the root is still / I think. I believe this configuration would vary if we had a monorepo containing many independent Gradle projects in various subdirectories.
I found an example in kotlin-logging and they use / too.