Skip to content

chore: Add Dependabot version-update cooldown#700

Open
ld-repository-standards[bot] wants to merge 1 commit into
v8from
ld-github-standards/add-dependabot-cooldown
Open

chore: Add Dependabot version-update cooldown#700
ld-repository-standards[bot] wants to merge 1 commit into
v8from
ld-github-standards/add-dependabot-cooldown

Conversation

@ld-repository-standards

@ld-repository-standards ld-repository-standards Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

This pull request was auto generated by the LaunchDarkly Github Standards automation platform.

  • Ensure every entry under updates in .github/dependabot.yml declares a cooldown of at least 7 days (default-days).
  • Add entries for detected package ecosystems that were not yet tracked by Dependabot.

Cooldown applies only to version updates; security updates bypass it, so critical CVE fixes are never delayed.

Ref: SEC-8058.


Note

Low Risk
CI-only configuration with no application runtime changes; security updates remain outside the cooldown.

Overview
Introduces Dependabot via a new .github/dependabot.yml, enabling automated dependency PRs for Docker, GitHub Actions, and Go modules on a weekly schedule.

Each ecosystem is configured with a 7-day version-update cooldown (default-days: 7), aligning with org standards so routine bumps are spaced out; security updates are not subject to this cooldown and can still land immediately.

Reviewed by Cursor Bugbot for commit 2e1037f. Bugbot is set up for automated code reviews on this repo. Configure here.

@ld-repository-standards ld-repository-standards Bot requested a review from a team June 17, 2026 06:28
@ld-repository-standards ld-repository-standards Bot requested a review from a team as a code owner June 17, 2026 06:28
@ld-repository-standards ld-repository-standards Bot requested a review from a team June 17, 2026 06:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant