Repository navigation
Automated release of 37.0.2 upstream release 37.0 1793913969 - #2772
Merged
Conversation
--- updated-dependencies: - dependency-name: aiohttp dependency-version: 3.14.4 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [helm/kind-action](https://github.com/helm/kind-action) from 1.15.0 to 1.15.1. - [Release notes](https://github.com/helm/kind-action/releases) - [Commits](helm/kind-action@06c1ae1...1544676) --- updated-dependencies: - dependency-name: helm/kind-action dependency-version: 1.15.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Updates the requirements on [pydantic](https://github.com/pydantic/pydantic) to permit the latest version. - [Release notes](https://github.com/pydantic/pydantic/releases) - [Changelog](https://github.com/pydantic/pydantic/blob/main/HISTORY.md) - [Commits](pydantic/pydantic@v2.13.5...v2.14.0) --- updated-dependencies: - dependency-name: pydantic dependency-version: 2.14.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
--- updated-dependencies: - dependency-name: aiohttp dependency-version: 3.14.5 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
websocket_proxycare() decoded the proxy-authorization header and split it on every ':', then indexed auth[0] and auth[1]. RFC 7617 allows ':' in the password (only the user-id may not contain one), so any proxy password containing a colon was silently truncated to the text before the first colon, sending the wrong credentials to the proxy. A header with no colon at all raised an unhandled IndexError. Split on the first colon only and only set http_proxy_auth when a password half is actually present.
Updates the requirements on [pydantic](https://github.com/pydantic/pydantic) to permit the latest version. - [Release notes](https://github.com/pydantic/pydantic/releases) - [Changelog](https://github.com/pydantic/pydantic/blob/main/HISTORY.md) - [Commits](pydantic/pydantic@v2.14.0...v2.14.1) --- updated-dependencies: - dependency-name: pydantic dependency-version: 2.14.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
The tests referenced socket.TCP_KEEPIDLE, which macOS does not define (it uses TCP_KEEPALIVE; keepalive.py already handles this), and expected SO_KEEPALIVE to read back as exactly 1, but macOS returns a non-zero flag.
Dependabot raised certifi from >=14.05.14 to >=2026.7.22, which makes the client impossible to install next to an application that pins an older certifi. The client only calls certifi.where(), which every release provides. Lower the bound to 2024.7.4, the oldest release without a known advisory (CVE-2024-39689), and set versioning-strategy to widen for pip so Dependabot keeps the ranges of this library open instead of raising the lower bound on every new release.
parse_quantity and format_quantity only rejected 'ki' among the binary
suffixes, so 'mi', 'ni' and 'ui' were accepted as base-1024 negative
exponents (e.g. parse_quantity('1mi') == 1/1024). Binary suffixes are limited
to Ki, Mi, Gi, Ti, Pi and Ei.
Updates the requirements on [pluggy](https://github.com/pytest-dev/pluggy) to permit the latest version. - [Changelog](https://github.com/pytest-dev/pluggy/blob/main/CHANGELOG.rst) - [Commits](pytest-dev/pluggy@1.6.0...1.7.0) --- updated-dependencies: - dependency-name: pluggy dependency-version: 1.7.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Updates the requirements on [setuptools](https://github.com/pypa/setuptools) to permit the latest version. - [Release notes](https://github.com/pypa/setuptools/releases) - [Changelog](https://github.com/pypa/setuptools/blob/main/NEWS.rst) - [Commits](pypa/setuptools@v84.0.0...v84.2.0) --- updated-dependencies: - dependency-name: setuptools dependency-version: 84.2.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Updates the requirements on [setuptools](https://github.com/pypa/setuptools) to permit the latest version. - [Release notes](https://github.com/pypa/setuptools/releases) - [Changelog](https://github.com/pypa/setuptools/blob/main/NEWS.rst) - [Commits](pypa/setuptools@v84.2.0...v84.2.1) --- updated-dependencies: - dependency-name: setuptools dependency-version: 84.2.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Updates the requirements on [python-dateutil](https://github.com/dateutil/dateutil) to permit the latest version. - [Release notes](https://github.com/dateutil/dateutil/releases) - [Changelog](https://github.com/dateutil/dateutil/blob/master/NEWS) - [Commits](dateutil/dateutil@2.8.2...3.0.0) --- updated-dependencies: - dependency-name: python-dateutil dependency-version: 3.0.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 7.0.0 to 7.1.0. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@5fda3b9...6d4fd22) --- updated-dependencies: - dependency-name: actions/setup-python dependency-version: 7.1.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Updates the requirements on [pydantic](https://github.com/pydantic/pydantic) to permit the latest version. - [Release notes](https://github.com/pydantic/pydantic/releases) - [Changelog](https://github.com/pydantic/pydantic/blob/v2.14.2/HISTORY.md) - [Commits](pydantic/pydantic@v2.14.1...v2.14.2) --- updated-dependencies: - dependency-name: pydantic dependency-version: 2.14.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
yliaog
force-pushed
the
automated-release-of-37.0.2-upstream-release-37.0-1793913969
branch
from
November 5, 2026 21:35
8bcdbf0 to
e38039f
Compare
Contributor
Author
|
/assign @roycaihw |
roycaihw
reviewed
Nov 5, 2026
|
|
||
| Kubernetes API Version: v1.37.2 | ||
|
|
||
|
|
Member
There was a problem hiding this comment.
Anything worth documented in the changelog for cutting a new release?
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: roycaihw, yliaog The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubernetes-prow
Bot
merged commit Nov 5, 2026
9e2647a
into
kubernetes-client:release-37.0
7 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind bug
What this PR does / why we need it:
Automated release of 37.0.2 upstream release 37.0 1793913969
Which issue(s) this PR fixes:
Fixes #
#2733
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: