## Changelog since v1.12.4

### Other notable changes

* kubectl: fixed an issue with "too old resource version" errors continuously appearing when calling `kubectl delete` ([#72825](https://github.com/kubernetes/kubernetes/pull/72825), [@liggitt](https://github.com/liggitt))

  When the scheduling queue receives a cluster event, before moving each Pod from unschedulable pod pool to activeQ/backoffQ, it will call QueueingHintFn of plugins that rejected each Pod in the previous scheduling cycle.
  Depending on the value returned from QueueingHintFn, the scheduling queue changes how it queues each Pod:
  - if more than one QueueingHintFn returns QueueImmediately, it queues Pod to activeQ.

k.Bytes(c.N), } fipsPCT(c, priv) return priv, nil } // randomPoint returns a random scalar and the corresponding point using a // procedure equivalent to FIPS 186-5, Appendix A.2.2 (ECDSA Key Pair Generation // by Rejection Sampling) and to Appendix A.3.2 (Per-Message Secret Number // Generation of Private Keys by Rejection Sampling) or Appendix A.3.3 // (Per-Message Secret Number Generation for Deterministic ECDSA) followed by // Step 5 of Section 6.4.1. func randomPoint[P Point[P]](c *Curve[P], generate...

          <description>
            <![CDATA[
            Whether the directory described by this source element should be included in the build.
            This flag provides an easy way to include or exclude some sources depending, for example,
            o property values defined in profiles. A use case is including optional resources only
            when the user confirmed a license agreement.

- golang.org/x/time: 9d24e82 → 555d28b
- golang.org/x/tools: 65e3620 → c1934b7
- golang.org/x/xerrors: a985d34 → 9bdfabe
- google.golang.org/api: 5213b80 → v0.15.1
- google.golang.org/appengine: v1.5.0 → v1.6.5
- google.golang.org/genproto: 24fa4b2 → cb27e3a
- google.golang.org/grpc: v1.26.0 → v1.27.0
- gopkg.in/check.v1: 788fd78 → 41f04d3
- honnef.co/go/tools: v0.0.1-2019.2.2 → v0.0.1-2019.2.3

        or provides additional installation flags.
    *   This dependency affected anyone installing TensorFlow 2.15 alongside
        NVIDIA CUDA dependencies via `pip install tensorflow[and-cuda]`.
    *   Depending on the installation method, TensorFlow 2.14 would be installed
        instead of 2.15, or users could receive an installation error due to
        those missing dependencies.

During server startup, prior to the server reporting healthy (via `/healthz`), not all API groups may be reported.
Wait for the server to report healthy (via `/healthz`) before depending on the information provided by the discovery APIs.
Additionally, since the information returned from the discovery APIs may change dynamically, a cache of the results should not be considered authoritative.

ap.ngrok.io
aparecida.br
apartments
api.gov.uk
api.stdlib.com
apigee.io
app
app-ionos.space
app.br
app.os.fedoraproject.org
app.os.stg.fedoraproject.org
app.render.com
appchizi.com
appengine.flow.ch
apple
applinzi.com
apps-1and1.com
apps-1and1.net
apps.fbsbx.com
apps.lair.io
appspacehosted.com
appspaceusercontent.com
appspot.com
appudo.net
aq
aq.it
aquarelle

- cloud.google.com/go/apigateway: v1.5.0 → v1.6.1
- cloud.google.com/go/apigeeconnect: v1.5.0 → v1.6.1
- cloud.google.com/go/apigeeregistry: v0.6.0 → v0.7.1
- cloud.google.com/go/appengine: v1.7.1 → v1.8.1
- cloud.google.com/go/area120: v0.7.1 → v0.8.1
- cloud.google.com/go/artifactregistry: v1.13.0 → v1.14.1
- cloud.google.com/go/asset: v1.13.0 → v1.14.1

enabled.([#51436](https://github.com/kubernetes/kubernetes/pull/51436))

* [Action required] The validation rule for metadata.initializers.pending[x].name is tightened. The initializer name must contain at least three segments, separated by dots. You can create objects with pending initializers and not rely on the API server to add pending initializers according to `initializerConfiguration`. If you do so, update the initializer name in the existing objects and the configuration files to...