Skip to content

remove support for v0.x release line #2576

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

Merged
merged 2 commits into from
Jul 31, 2025

Conversation

cjihrig
Copy link
Contributor

@cjihrig cjihrig commented Jul 29, 2025

This commit disables everything related to the old v0.x release line (the master branch in git). The v0.x git branch and old release artifacts will be left in tact.

Fixes: #2573

This commit disables everything related to the old v0.x release
line (the master branch in git). The v0.x git branch and old
release artifacts will be left in tact.
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jul 29, 2025
@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 29, 2025
push:
branches:
- master
push:
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The whitespace changes in this file were done automatically by my editor.

@brendandburns
Copy link
Contributor

Let's leave codeql and test so that if we get PRs we don't accidentally merge broken, malicious code without CI/CD.

It will only run if people send PRs.

@mstruebing
Copy link
Member

Nice LGTM to me but I will leave the final approval to @brendandburns.

Should we update the readme in the master branch with a big note that this is a deprecated branch as well?

@cjihrig
Copy link
Contributor Author

cjihrig commented Jul 30, 2025

Should we update the readme in the master branch with a big note that this is a deprecated branch as well?

No strong opinion on that, but it would have to be done as a separate PR.

@brendandburns
Copy link
Contributor

/lgtm
/approve

Thanks for cleaning this up. I'm not sure that we need to modify the master branch. We've already switched the default branch to main so in my opinion master is just another branch like any other.

But if someone wants to send a PR, I'm happy to merge it.

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 31, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brendandburns, cjihrig

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

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [brendandburns,cjihrig]

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

@k8s-ci-robot k8s-ci-robot merged commit 15f31cc into kubernetes-client:main Jul 31, 2025
9 checks passed
@cjihrig cjihrig deleted the rm-0.x branch July 31, 2025 15:17
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

End of life for v0.x release line
4 participants