Skip to content

chore: set Dependabot update intervals to monthly - #120

Merged
Matt (matt-evervault) merged 1 commit into
mainfrom
chore/dependabot-monthly
Aug 27, 2026
Merged

chore: set Dependabot update intervals to monthly#120
Matt (matt-evervault) merged 1 commit into
mainfrom
chore/dependabot-monthly

Conversation

@matt-evervault

Copy link
Copy Markdown
Contributor

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.interval from "daily" to "monthly" for all three ecosystem entries. Nothing else in the file was touched — open-pull-requests-limit: 0 is 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 ignore open-pull-requests-limit).

Ecosystem check

  • github-actions: .github/workflows/*.yml exists (codeql.yml, release.yml, test.yml), so directory: "/" is representative for this ecosystem.
  • gradle: The root build.gradle.kts lives 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, and sampleapplication/build.gradle.kts all live outside the root and are not directly covered by directory: "/". Dependabot's gradle updater does resolve module structure via settings.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.
  • npm: A root package.json exists (private package with @changesets/cli as the only devDependency, used for versioning scripts), so the npm entry is real, not vestigial.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@matt-evervault Matt (matt-evervault) self-assigned this Aug 27, 2026
@ev-vaultkeeper

Copy link
Copy Markdown

Vaultkeeper Commands

Mention @ev-vaultkeeper <command> in a PR review thread:

  • review — Review this PR and leave a review.
  • address-comments — Push commits that address the review feedback on this PR.
  • fix-ci — Investigate the failing CI on this PR and push a fix.

You can also request evervault-dependencies as a reviewer to trigger a review.

@changeset-bot

changeset-bot Bot commented Aug 27, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 363f143

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@matt-evervault
Matt (matt-evervault) marked this pull request as ready for review August 27, 2026 11:06
@matt-evervault
Matt (matt-evervault) requested a review from a team as a code owner August 27, 2026 11:06
@matt-evervault
Matt (matt-evervault) merged commit bc53fee into main Aug 27, 2026
5 checks passed
@matt-evervault
Matt (matt-evervault) deleted the chore/dependabot-monthly branch August 27, 2026 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants