Skip to content

ci(dep): update dependabot configuration #2338

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 16, 2025
Merged

ci(dep): update dependabot configuration #2338

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion .github/dependabot.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
# Please see the documentation for all configuration options:
# https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file

version: 2
updates:
- package-ecosystem: gomod
Expand All @@ -15,6 +14,12 @@ updates:
ignore:
- dependency-name: k8s.io/*
update-types: [version-update:semver-major, version-update:semver-minor]
commit-message:
include: scope
open-pull-requests-limit: 5
Copy link
Collaborator

@SamYuan1990 SamYuan1990 Oct 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need limit PR number to 5?
in an edge case, we meet this limitation and a new cve happens in one of our dependency.
a new patch is ready on upstream, can we benefits from https://github.com/sustainable-computing-io/kepler/security/dependabot to open a new PR as #2247 for now, over the limitation, having the 6 PRs and patched?

Copy link
Collaborator

@sthaha sthaha Oct 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets start with 5 (since the PR is already mergable). If in future, we have to raise the number, we can deal with it then.

labels:
- dependencies
- go
- package-ecosystem: github-actions
directory: /
schedule:
Expand All @@ -24,3 +29,9 @@ updates:
github-actions:
patterns:
- "*"
commit-message:
include: scope
open-pull-requests-limit: 5
labels:
- dependencies
- github-actions
Loading