Skip to content

test: update integration test Dockerfiles with Dependabot #45497

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

test: update integration test Dockerfiles with Dependabot #45497

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
15 changes: 14 additions & 1 deletion .github/dependabot.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ updates:

- package-ecosystem: gomod
directory: /
# Workaround to satisfy Dependabot's unique constraint (needs unique 'package-ecosystem', 'directory', 'target-branch' tuples)
# Workaround to satisfy Dependabot's unique constraint (needs unique 'package-ecosystem', 'directory', 'target-branch' tuples)
# for duplicate package-ecosystem configurations: https://github.com/dependabot/dependabot-core/issues/1778#issuecomment-1988140219
target-branch: main
schedule:
Expand Down Expand Up @@ -93,6 +93,19 @@ updates:
- "github.com/StackExchange/wmi"
open-pull-requests-limit: 5

# Update integration test container images
- package-ecosystem: "docker"
directories:
# Starting with the sredis image, we might want to add other images later.
- '/testing/environments/docker/sredis'
schedule:
interval: "weekly"
day: "sunday"
time: "23:29"
labels:
- automation
- dependabot
Copy link
Member

@rdner rdner Jul 22, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

we need backport labels and the data-plane team label here.

Copy link
Member

Choose a reason for hiding this comment

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

Scrap that. I think we don't need backports for dependency updates and the PRs don't need an approval if the CI succeeds, so it's good as it is.


# GitHub actions
- package-ecosystem: "github-actions"
directories:
Expand Down
Loading