Skip to content

Group dependabot updates by package origin#51

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
sebrandon1:dependabot-k8s-group
Jun 8, 2026
Merged

Group dependabot updates by package origin#51
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
sebrandon1:dependabot-k8s-group

Conversation

@sebrandon1

@sebrandon1 sebrandon1 commented Jan 5, 2026

Copy link
Copy Markdown
Member

Summary

  • Add k8s and openshift groups to consolidate related package updates into single PRs
  • Groups k8s.io/* and sigs.k8s.io/* packages together for coordinated updates
  • Groups github.com/openshift/* packages together
  • Catches remaining dependencies in other-go-modules group

This reduces PR noise and makes dependency updates easier to review.

Related PRs

This change is part of a coordinated effort across multiple OpenShift repositories:

Tracked by: CNFCERT-1301

Test plan

  • Verify dependabot.yml syntax is valid
  • Wait for next dependabot run to confirm groups are applied correctly

🤖 Generated with Claude Code

Add k8s and openshift groups to consolidate related package updates:
- k8s: Groups k8s.io/* and sigs.k8s.io/* packages
- openshift: Groups github.com/openshift/* packages
- other-go-modules: Catches remaining dependencies

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@openshift-bot

Copy link
Copy Markdown

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 9, 2026
@karampok

karampok commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

/approve
/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 8, 2026
@openshift-ci

openshift-ci Bot commented Jun 8, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: karampok, sebrandon1

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 8, 2026
@karampok

karampok commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

/verified by ci

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jun 8, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@karampok: This PR has been marked as verified by ci.

Details

In response to this:

/verified by ci

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci

openshift-ci Bot commented Jun 8, 2026

Copy link
Copy Markdown

@sebrandon1: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot Bot merged commit ef685ce into openshift:main Jun 8, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants