Skip to content
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.

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

Enable dependabot to update released branches #1675

Open
jingxu97 opened this issue Nov 8, 2024 · 3 comments
Open

Enable dependabot to update released branches #1675

jingxu97 opened this issue Nov 8, 2024 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@jingxu97
Copy link

jingxu97 commented Nov 8, 2024

What would you like to be added:

Enable dependabot to update gomod for released branches

Why is this needed:

Similar to Kubernetes, we could have support for released branches, e.g., currently 1.30 and 1.29. Could we enable dependabot to update those release branches too?

@jingxu97 jingxu97 added kind/feature Categorizes issue or PR as related to a new feature. sig/node Categorizes an issue or PR as relevant to SIG Node. labels Nov 8, 2024
@SergeyKanzhelev
Copy link
Member

do you know the way?

these seems to indicate that it is not possible: dependabot/dependabot-core#2159 + dependabot/dependabot-core#2511

@saschagrunert
Copy link
Member

Right now we don't have a maintenance plan for the release branches. It would trigger more work on our side to release after a modification semi-automatically happened to them. So, I'm in favor of not doing the suggested change event if it would be technically possible.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Development

No branches or pull requests

5 participants