chore: set Dependabot update intervals to monthly - #120
Merged
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Vaultkeeper Commands Mention
You can also request |
|
Matt (matt-evervault)
marked this pull request as ready for review
August 27, 2026 11:06
Cian Tuohy (CianT123)
approved these changes
Aug 27, 2026
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
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.
Why
Slow down Dependabot's update cadence from daily to monthly for all three ecosystems (github-actions, gradle, npm) configured in
.github/dependabot.yml.How
Changed
schedule.intervalfrom"daily"to"monthly"for all three ecosystem entries. Nothing else in the file was touched —open-pull-requests-limit: 0is left in place on all three entries, which already suppresses version-update PRs entirely, so this interval change only affects the cadence of security-update PRs (which ignoreopen-pull-requests-limit).Ecosystem check
.github/workflows/*.ymlexists (codeql.yml,release.yml,test.yml), sodirectory: "/"is representative for this ecosystem.build.gradle.ktslives at/, but the project is multi-module —evervault-cages/build.gradle.kts,evervault-core/build.gradle.kts,evervault-enclaves/build.gradle.kts,evervault-inputs/build.gradle.kts,examples/shared/build.gradle.kts, andsampleapplication/build.gradle.ktsall live outside the root and are not directly covered bydirectory: "/". Dependabot's gradle updater does resolve module structure viasettings.gradle.kts, so root-only config may still cover the whole project, but this wasn't verified end-to-end — flagging for awareness, not changing as part of this PR.package.jsonexists (private package with@changesets/clias the only devDependency, used for versioning scripts), so the npm entry is real, not vestigial.