Skip to content

Conversation

@sonalgaud12
Copy link

What type of PR is this?
/kind bug

What this PR does / why we need it:
Excludes k8s.io/* packages from automatic dependabot updates to prevent compatibility breaking changes.

Which issue(s) this PR fixes:
Fixes #1403

Special notes for your reviewer:
Changed from grouping k8s.io packages to completely ignoring them as suggested by the maintainer.

Does this PR introduce a user-facing change?:

NONE

@kmesh-bot kmesh-bot added the kind/bug Something isn't working label Jul 29, 2025
@kmesh-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign supercharge-xsy for approval. For more information see the Kubernetes Code Review Process.

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

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

@kmesh-bot
Copy link
Collaborator

Welcome @sonalgaud12! It looks like this is your first PR to kmesh-net/kmesh 🎉

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @sonalgaud12, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

I've updated the Dependabot configuration to prevent automatic updates for k8s.io dependencies. This change is crucial to avoid potential compatibility-breaking changes that could arise from these updates, ensuring the stability of our project.

Highlights

  • Dependabot Configuration Update: I've modified the .github/dependabot.yml file to exclude all k8s.io/* packages from Dependabot's automatic updates. This shifts from a previous approach of grouping these dependencies to completely ignoring them, as suggested by a maintainer, to prevent compatibility issues.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request correctly updates the Dependabot configuration to ignore k8s.io dependencies, which is a sensible approach to prevent automated updates from causing breaking changes. The implementation is correct. I have one suggestion to add a comment explaining this decision, which will improve the maintainability of the configuration file.

patterns:
- "k8s.io/*"
ignore:
- dependency-name: "k8s.io/*"

Choose a reason for hiding this comment

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

medium

For improved maintainability, consider adding a comment to explain why k8s.io dependencies are being ignored. This will provide valuable context for future contributors who might wonder why these dependencies are not being updated by Dependabot, and it clarifies that this is an intentional decision.

      # Exclude k8s.io dependencies from automated updates to prevent breaking changes.
      # These are updated manually. See issue #1403.
      - dependency-name: "k8s.io/*"

@sonalgaud12
Copy link
Author

@hzxuzhonghu Please review and let me know if any changes required. Thanks

@codecov
Copy link

codecov bot commented Jul 29, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 36.97%. Comparing base (65d8180) to head (6a18628).
⚠️ Report is 5 commits behind head on main.
see 2 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 76e80d1...6a18628. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/bug Something isn't working size/XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bump dependencies

2 participants