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

WIP: Prep 2.13.0 #2419

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

WIP: Prep 2.13.0 #2419

wants to merge 2 commits into from

Conversation

mrueg
Copy link
Member

@mrueg mrueg commented Jun 14, 2024

What this PR does / why we need it:
Preparing for next release.
How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
None
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2406

@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 14, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mrueg

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:

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 added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jun 14, 2024
@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 14, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jun 14, 2024
@mrueg mrueg added this to the v2.13.0 milestone Jun 14, 2024
@CatherineF-dev
Copy link
Contributor

Use 2.13.0 instead #2375

@CatherineF-dev CatherineF-dev mentioned this pull request Jun 14, 2024
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 18, 2024
@grigoni
Copy link

grigoni commented Jun 21, 2024

Hi folks
To my understanding there will be no 2.12.x release
This opens two questions:
Will this release also support k8s 1.29.x?
How this project manages CVEs for current supported K8s versions?

thanks
Gianandrea

@rexagod
Copy link
Member

rexagod commented Jun 23, 2024

Can we include #2418 as well?

@jeremyrickard
Copy link

Hey folks, do you need any help with these releases? Is there something community members can help with?

@mrueg
Copy link
Member Author

mrueg commented Jun 28, 2024

Thanks for the offer! There are two more issues, we would want to resolve before the next release: https://github.com/kubernetes/kube-state-metrics/milestone/6

In general, yes. If someone in the community would want to help increasing the release cadence that would be super helpful! Let's chat in #kube-state-metrics in k8s slack.

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. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When is the next release scheduled? Will it be based on "Debian GNU/Linux 12 (Bookworm)"?
6 participants