✨ Release envtest v1.37.0-beta.0

[dongjiang1989]

Go version: https://github.com/kubernetes/kubernetes/blob/v1.37.0-beta.0/.go-version
ETCD version: https://github.com/kubernetes/kubernetes/blob/v1.37.0-beta.0/cmd/kubeadm/app/constants/constants.go#L330

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[sbueringer]

Is there a concrete need to have envtest binaries published for this beta? If not, I would prefer not investing time in it (publishing envtest binaries requires manual work after this PR is merged)

[dongjiang1989]

Is there a concrete need to have envtest binaries published for this beta? If not, I would prefer not investing time in it (publishing envtest binaries requires manual work after this PR is merged)

Hmmmm.... We have concrete internal demand for envtest binaries.
Is it possible to automate the publishing via GitHub Actions?

[sbueringer]

Is there a concrete need to have envtest binaries published for this beta? If not, I would prefer not investing time in it (publishing envtest binaries requires manual work after this PR is merged)

Hmmmm.... We have concrete internal demand for envtest binaries. Is it possible to automate the publishing via GitHub Actions?

Specifically for this beta? (then it's fine) Or is the final GA release enough?

It's not possible to automate this because we are not allowed to open PRs from GitHub actions (xref: #1113 (comment), example: https://github.com/kubernetes-sigs/controller-tools/actions/runs/28243362791/job/83675744586)

(we had this automated in the past, or rather still have it, but it fails at the PR creation step now)