fix(deps): update all non-major go dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/cloudnative-pg/cloudnative-pg	v1.24.0 -> v1.25.1
github.com/cloudnative-pg/cnpg-i	v0.0.0-20240910144444-89d2e00640c5 -> v0.1.0
github.com/cloudnative-pg/cnpg-i-machinery	v0.0.0-20240910161515-95a7e6cb16f9 -> v0.1.2
github.com/spf13/cobra	v1.8.1 -> v1.9.1
google.golang.org/grpc	v1.66.1 -> v1.70.0
k8s.io/api	v0.31.0 -> v0.32.2
k8s.io/apimachinery	v0.31.0 -> v0.32.2
sigs.k8s.io/controller-runtime	v0.19.0 -> v0.20.2

---

Release Notes

cloudnative-pg/cloudnative-pg (github.com/cloudnative-pg/cloudnative-pg)

v1.25.1

Compare Source

Release Date: February 28, 2025

Enhancements

• Introduced a startup probe for the operator to enhance reliability and prevent premature liveness probe failures during initialization. (#​7008)
• Added support for using the -r service with the Pooler. (#​6868)
• Introduced an optional --ttl flag for the pgbench plugin, enabling automatic deletion of completed jobs after a user-defined duration. (#​6701)
• Marked known error messages from the Azure CSI Driver for volume snapshots as retryable, improving resilience. (#​6906)
• Updated the default PostgreSQL version to 17.4 for new cluster definitions. (#​6960)

Security

• The operator image build process has been enhanced to strengthen security and transparency. Images are now signed with cosign, and OCI attestations are generated, incorporating the Software Bill of Materials (SBOM) and provenance data. Additionally, OCI annotations have been added to improve traceability and ensure the integrity of the images.

Bug Fixes

• Fixed inconsistent behavior in default probe knob values when .spec.probes is defined, ensuring users can override all settings, including failureThreshold. If unspecified in the startup probe, failureThreshold is now correctly derived from .spec.startupDelay / periodSeconds (default: 10, now overridable). The same logic applies to liveness probes via .spec.livenessProbeTimeout. (#​6656)
• Managed service ports now take precedence over default operator-defined ports. (#​6474)
• Fixed an issue where WAL metrics were unavailable after an instance restart until a configuration change was applied. (#​6816)
• Fixed an issue in monolithic database import where role import was skipped if no roles were specified. (#​6646)
• Added support for new metrics introduced in PgBouncer 1.24. (#​6630)
• Resolved an issue where Database, Publication, and Subscription CRDs became stuck in cluster resource has been deleted, skipping reconciliation after cluster rehydration. This patch forces status.observedGeneration to zero, ensuring proper reconciliation. (#​6607)
• Improved handling of replication-sensitive parameter reductions by ensuring timely reconciliation after primary server restarts. (#​6440)
• Introduced a new isWALArchiver flag in the CNPG-I plugin configuration, allowing users to designate a plugin as a WAL archiver. This enables seamless migration from in-tree Barman Cloud support to the plugin while maintaining WAL archive consistency. (#​6593)
• Ensured override.conf is consistently included in postgresql.conf during replica cluster bootstrapping, preventing replication failures due to missing configuration settings. (#​6808)
• Ensured override.conf is correctly initialized before invoking pg_rewind to prevent failures during primary role changes. (#​6670)
• Enhanced webhook responses to return both warnings and errors when applicable, improving diagnostic accuracy. (#​6579)
• Ensured the operator version is correctly reconciled. (#​6496)
• Improved PostgreSQL version detection by using a more precise check of the data directory. (#​6659)
• Volume Snapshot Backups:
  • Fixed an issue where unused backup connections were not properly cleaned up. (#​6882)
  • Ensured the instance manager closes stale PostgreSQL connections left by failed volume snapshot backups. (#​6879)
  • Prevented the operator from starting a new volume snapshot backup while another is already in progress. (#​6890)
• cnpg plugin:
  • Restored functionality of the promote plugin command. (#​6476)
  • Enhanced kubectl cnpg report --logs <cluster> to collect logs from all containers, including sidecars. (#​6636)
  • Ensured pgbench jobs can run when a Cluster uses an ImageCatalog. (#​6868)

Technical Enhancements

• Added support for Kubernetes client-gen, enabling automated generation of Go clients for all CloudNativePG CRDs. (#​6695)

v1.25.0

Compare Source

Release Date: December 23, 2024

Features

• Declarative Database Management: Introduce the Database Custom Resource Definition (CRD), enabling users to create and manage PostgreSQL databases declaratively within a cluster. (#​5325)

• Logical Replication Management: Add Publication and Subscription CRDs for declarative management of PostgreSQL logical replication. These simplify replication setup and facilitate online migrations to CloudNativePG. (#​5329)

• Experimental Support for CNPG-I: Introducing CNPG-I (CloudNativePG Interface), a standardized framework designed to extend CloudNativePG functionality through third-party plugins and foster the growth of the CNPG ecosystem. The Barman Cloud Plugin serves as a live example, illustrating how plugins can be developed to enhance backup and recovery workflows. Although CNPG-I support is currently experimental, it offers a powerful approach to extending CloudNativePG without modifying the operator’s core code—akin to PostgreSQL extensions. We welcome community feedback and contributions to shape this exciting new capability.

Enhancements

• Add the dataDurability option to the .spec.postgresql.synchronous stanza, allowing users to choose between required (default) or preferred durability in synchronous replication. (#​5878)
• Enable customization of startup, liveness, and readiness probes through the .spec.probes stanza. (#​6266)
• Support additional pg_dump and pg_restore options to enhance database import flexibility. (#​6214)
• Add support for maxConcurrentReconciles in the CloudNativePG controller and set the default to 10, improving the operator's ability to efficiently manage larger deployments out of the box. (#​5678)
• Add the cnpg.io/userType label to secrets generated for predefined users, specifically superuser and app. (#​4392)
• Improved validation for the spec.schedule field in ScheduledBackups, raising warnings for potential misconfigurations. (#​5396)
• cnpg plugin:
  • Enhance the backup command to support plugins. (#​6045)
  • Honor the User-Agent header in HTTP requests with the API server. (#​6153)

Bug Fixes

• Ensure the former primary flushes its WAL file queue to the archive before re-synchronizing as a replica, reducing recovery times and enhancing data consistency during failovers. (#​6141)
• Clean the WAL volume along with the PGDATA volume during bootstrap. (#​6265)
• Update the operator to set the cluster phase to Unrecoverable when all previously generated PersistentVolumeClaims are missing. (#​6170)
• Fix the parsing of the synchronous_standby_names GUC when .spec.postgresql.synchronous.method is set to first. (#​5955)
• Resolved a potential race condition when patching certain conditions in CRD statuses, improving reliability in concurrent updates. (#​6328)
• Correct role changes to apply at the transaction level instead of the database context. (#​6064)
• Remove the primary_slot_name definition from the override.conf file on the primary to ensure it is always empty. (#​6219)
• Configure libpq environment variables, including PGHOST, in PgBouncer pods to enable seamless access to the pgbouncer virtual database using psql from within the container. (#​6247)
• Remove unnecessary updates to the Cluster status when verifying changes in the image catalog. (#​6277)
• Prevent panic during recovery from an external server without proper backup configuration. (#​6300)
• Resolved a key collision issue in structured logs, where the name field was inconsistently used to log two distinct values. (#​6324)
• Ensure proper quoting of the inRoles field in SQL statements to prevent syntax errors in generated SQL during role management. (#​6346)
• cnpg plugin:
  • Ensure the kubectl context is properly passed in the psql command. (#​6257)
  • Avoid displaying physical backups block when empty with status command. (#​5998)

Supported Versions

• Kubernetes: 1.32, 1.31, 1.30, and 1.29
• PostgreSQL: 17, 16, 15, 14, and 13
  • Default image: PostgreSQL 17.2
  • Officially dropped support for PostgreSQL 12
  • PostgreSQL 13 support ends on November 12, 2025

v1.24.3

Compare Source

Release Date: February 28, 2025

Enhancements

• Introduced a startup probe for the operator to enhance reliability and prevent premature liveness probe failures during initialization. (#​7008)
• Added support for using the -r service with the Pooler. (#​6868)
• Introduced an optional --ttl flag for the pgbench plugin, enabling automatic deletion of completed jobs after a user-defined duration. (#​6701)
• Marked known error messages from the Azure CSI Driver for volume snapshots as retryable, improving resilience. (#​6906)
• Updated the default PostgreSQL version to 17.4 for new cluster definitions. (#​6960)

Security

• The operator image build process has been enhanced to strengthen security and transparency. Images are now signed with cosign, and OCI attestations are generated, incorporating the Software Bill of Materials (SBOM) and provenance data. Additionally, OCI annotations have been added to improve traceability and ensure the integrity of the images.

Bug Fixes

• Fixed inconsistent behavior in default probe knob values when .spec.probes is defined, ensuring users can override all settings, including failureThreshold. If unspecified in the startup probe, failureThreshold is now correctly derived from .spec.startupDelay / periodSeconds (default: 10, now overridable). The same logic applies to liveness probes via .spec.livenessProbeTimeout. (#​6656)
• Managed service ports now take precedence over default operator-defined ports. (#​6474)
• Fixed an issue where WAL metrics were unavailable after an instance restart until a configuration change was applied. (#​6816)
• Fixed an issue in monolithic database import where role import was skipped if no roles were specified. (#​6646)
• Added support for new metrics introduced in PgBouncer 1.24. (#​6630)
• Improved handling of replication-sensitive parameter reductions by ensuring timely reconciliation after primary server restarts. (#​6440)
• Introduced a new isWALArchiver flag in the CNPG-I plugin configuration, allowing users to designate a plugin as a WAL archiver. This enables seamless migration from in-tree Barman Cloud support to the plugin while maintaining WAL archive consistency. (#​6593)
• Ensured override.conf is consistently included in postgresql.conf during replica cluster bootstrapping, preventing replication failures due to missing configuration settings. (#​6808)
• Ensured override.conf is correctly initialized before invoking pg_rewind to prevent failures during primary role changes. (#​6670)
• Enhanced webhook responses to return both warnings and errors when applicable, improving diagnostic accuracy. (#​6579)
• Ensured the operator version is correctly reconciled. (#​6496)
• Improved PostgreSQL version detection by using a more precise check of the data directory. (#​6659)
• Volume Snapshot Backups:
  • Fixed an issue where unused backup connections were not properly cleaned up. (#​6882)
  • Ensured the instance manager closes stale PostgreSQL connections left by failed volume snapshot backups. (#​6879)
  • Prevented the operator from starting a new volume snapshot backup while another is already in progress. (#​6890)
• cnpg plugin:
  • Restored functionality of the promote plugin command. (#​6476)
  • Enhanced kubectl cnpg report --logs <cluster> to collect logs from all containers, including sidecars. (#​6636)
  • Ensured pgbench jobs can run when a Cluster uses an ImageCatalog. (#​6868)

Technical Enhancements

• Added support for Kubernetes client-gen, enabling automated generation of Go clients for all CloudNativePG CRDs. (#​6695)

v1.24.2

Compare Source

Release Date: December 23, 2024

Enhancements

• Enable customization of startup, liveness, and readiness probes through the .spec.probes stanza. (#​6266)
• Add the cnpg.io/userType label to secrets generated for predefined users, specifically superuser and app. (#​4392)
• Improved validation for the spec.schedule field in ScheduledBackups, raising warnings for potential misconfigurations. (#​5396)
• cnpg plugin:
  • Honor the User-Agent header in HTTP requests with the API server. (#​6153)

Bug Fixes

• Ensure the former primary flushes its WAL file queue to the archive before re-synchronizing as a replica, reducing recovery times and enhancing data consistency during failovers. (#​6141)
• Clean the WAL volume along with the PGDATA volume during bootstrap. (#​6265)
• Update the operator to set the cluster phase to Unrecoverable when all previously generated PersistentVolumeClaims are missing. (#​6170)
• Fix the parsing of the synchronous_standby_names GUC when .spec.postgresql.synchronous.method is set to first. (#​5955)
• Resolved a potential race condition when patching certain conditions in CRD statuses, improving reliability in concurrent updates. (#​6328)
• Correct role changes to apply at the transaction level instead of the database context. (#​6064)
• Remove the primary_slot_name definition from the override.conf file on the primary to ensure it is always empty. (#​6219)
• Configure libpq environment variables, including PGHOST, in PgBouncer pods to enable seamless access to the pgbouncer virtual database using psql from within the container. (#​6247)
• Remove unnecessary updates to the Cluster status when verifying changes in the image catalog. (#​6277)
• Prevent panic during recovery from an external server without proper backup configuration. (#​6300)
• Resolved a key collision issue in structured logs, where the name field was inconsistently used to log two distinct values. (#​6324)
• Ensure proper quoting of the inRoles field in SQL statements to prevent syntax errors in generated SQL during role management. (#​6346)
• cnpg plugin:
  • Ensure the kubectl context is properly passed in the psql command. (#​6257)
  • Avoid displaying physical backups block when empty with status command. (#​5998)

v1.24.1

Compare Source

Release date: Oct 16, 2024

Enhancements:

• Remove the use of pg_database_size from the status probe, as it caused high resource utilization by scanning the entire PGDATA directory to compute database sizes. The kubectl status plugin will now rely on du to provide detailed size information retrieval (#​5689).
• Add the ability to configure the full_page_writes parameter in PostgreSQL. This setting defaults to on, in line with PostgreSQL's recommendations (#​5516).
• Plugin:
  • Add the logs pretty command in the cnpg plugin to read a log stream from standard input and output a human-readable format, with options to filter log entries (#​5770)
  • Enhance the status command by allowing multiple -v options to increase verbosity for more detailed output (#​5765).
  • Add support for specifying a custom Docker image using the --image flag in the pgadmin4 plugin command, giving users control over the Docker image used for pgAdmin4 deployments (#​5515).

Fixes:

• Resolve an issue with concurrent status updates when demoting a primary to a designated primary, ensuring smoother transitions during cluster role changes (#​5755).
• Ensure that replica PodDisruptionBudgets (PDB) are removed when scaling down to two instances, enabling easier maintenance on the node hosting the replica (#​5487).
• Prioritize full rollout over inplace restarts (#​5407).
• When using .spec.postgresql.synchronous, ensure that the synchronous_standby_names parameter is correctly set, even when no replicas are reachable (#​5831).
• Fix an issue that could lead to double failover in cases of lost connectivity (#​5788).
• Correctly set the TMPDIR and PSQL_HISTORY environment variables for pods and jobs, improving temporary file and history management (#​5503).
• Plugin:
  • Resolve a race condition in the logs cluster command (#​5775).
  • Display the potential sync status in the status plugin (#​5533).
  • Fix the issue where pods deployed by the pgadmin4 command didn’t have a writable home directory (#​5800).

Supported versions

• PostgreSQL 17 (PostgreSQL 17.0 is the default image)

cloudnative-pg/cnpg-i-machinery (github.com/cloudnative-pg/cnpg-i-machinery)

v0.1.2

Compare Source

Bug Fixes

• deps: set cloudnative-pg API version to latest (#​144) (2de477f)

v0.1.1

Compare Source

Bug Fixes

• deps: downgrade go-grpc-middleware/v2 to v2.2.0 (#​139) (f02364a)

spf13/cobra (github.com/spf13/cobra)

v1.9.1

Compare Source

🐛 Fixes

• Fix CompletionFunc implementation by @​ccoVeille in https://github.com/spf13/cobra/pull/2234
• Revert "Make detection for test-binary more universal (#​2173)" by @​marckhouzam in https://github.com/spf13/cobra/pull/2235

Full Changelog: spf13/cobra@v1.9.0...v1.9.1

v1.9.0

Compare Source

✨ Features

• Allow linker to perform deadcode elimination for program using Cobra by @​aarzilli in https://github.com/spf13/cobra/pull/1956
• Add default completion command even if there are no other sub-commands by @​marckhouzam in https://github.com/spf13/cobra/pull/1559
• Add CompletionWithDesc helper by @​ccoVeille in https://github.com/spf13/cobra/pull/2231

🐛 Fixes

• Fix deprecation comment for Command.SetOutput by @​thaJeztah in https://github.com/spf13/cobra/pull/2172
• Replace deprecated ioutil usage by @​nirs in https://github.com/spf13/cobra/pull/2181
• Fix --version help and output for plugins by @​nirs in https://github.com/spf13/cobra/pull/2180
• Allow to reset the templates to the default by @​marckhouzam in https://github.com/spf13/cobra/pull/2229

🤖 Completions

• Make Powershell completion work in constrained mode by @​lstemplinger in https://github.com/spf13/cobra/pull/2196
• Improve detection for flags that accept multiple values by @​thaJeztah in https://github.com/spf13/cobra/pull/2210
• add CompletionFunc type to help with completions by @​ccoVeille in https://github.com/spf13/cobra/pull/2220
• Add similar whitespace escape logic to bash v2 completions than in other completions by @​kangasta in https://github.com/spf13/cobra/pull/1743
• Print ActiveHelp for bash along other completions by @​marckhouzam in https://github.com/spf13/cobra/pull/2076
• fix(completions): Complete map flags multiple times by @​gabe565 in https://github.com/spf13/cobra/pull/2174
• fix(bash): nounset unbound file filter variable on empty extension by @​scop in https://github.com/spf13/cobra/pull/2228

🧪 Testing

• Test also with go 1.23 by @​nirs in https://github.com/spf13/cobra/pull/2182
• Make detection for test-binary more universal by @​thaJeztah in https://github.com/spf13/cobra/pull/2173

✍🏼 Documentation

• docs: update README.md by @​eltociear in https://github.com/spf13/cobra/pull/2197
• Improve site formatting by @​nirs in https://github.com/spf13/cobra/pull/2183
• doc: add Conduit by @​raulb in https://github.com/spf13/cobra/pull/2230
• doc: azion project added to the list of CLIs that use cobra by @​maxwelbm in https://github.com/spf13/cobra/pull/2198
• Fix broken links in active_help.md by @​vuil in https://github.com/spf13/cobra/pull/2202
• chore: fix function name in comment by @​zhuhaicity in https://github.com/spf13/cobra/pull/2216

🔧 Dependency upgrades

• build(deps): bump github.com/cpuguy83/go-md2man/v2 from 2.0.5 to 2.0.6 by @​thaJeztah in https://github.com/spf13/cobra/pull/2206
• Update to latest go-md2man by @​mikelolasagasti in https://github.com/spf13/cobra/pull/2201
• Upgrade pflag dependencies for v1.9.0 by @​jpmcb in https://github.com/spf13/cobra/pull/2233

---

Thank you to all of our amazing contributors and all the great work that's been going into the completions feature!!

👋🏼 New Contributors

• @​gabe565 made their first contribution in https://github.com/spf13/cobra/pull/2174
• @​maxwelbm made their first contribution in https://github.com/spf13/cobra/pull/2198
• @​lstemplinger made their first contribution in https://github.com/spf13/cobra/pull/2196
• @​vuil made their first contribution in https://github.com/spf13/cobra/pull/2202
• @​mikelolasagasti made their first contribution in https://github.com/spf13/cobra/pull/2201
• @​zhuhaicity made their first contribution in https://github.com/spf13/cobra/pull/2216
• @​ccoVeille made their first contribution in https://github.com/spf13/cobra/pull/2220
• @​kangasta made their first contribution in https://github.com/spf13/cobra/pull/1743
• @​aarzilli made their first contribution in https://github.com/spf13/cobra/pull/1956

Full Changelog: spf13/cobra@v1.8.1...v1.9.0

grpc/grpc-go (google.golang.org/grpc)

v1.70.0: Release 1.70.0

Compare Source

Behavior Changes

• client: reject service configs containing an invalid retryPolicy in accordance with gRFCs A21 and A6. (#​7905)
  • Note that this is a potential breaking change for some users using an invalid configuration, but continuing to allow this behavior would violate our cross-language compatibility requirements.

New Features

• xdsclient: fallback to a secondary management server (if specified in the bootstrap configuration) when the primary is down is enabled by default. Can be disabled by setting the environment variable GRPC_EXPERIMENTAL_XDS_FALLBACK to false. (#​7949)
• experimental/credentials: experimental transport credentials are added which don't enforce ALPN. (#​7980)
  • These credentials will be removed in an upcoming grpc-go release. Users must not rely on these credentials directly. Instead, they should either vendor a specific version of gRPC or copy the relevant credentials into their own codebase if absolutely necessary.

Bug Fixes

• xds: fix a possible deadlock that happens when both the client application and the xDS management server (responsible for configuring the client) are using the xds:/// scheme in their target URIs. (#​8011)

Performance

• server: for unary requests, free raw request message data as soon as parsing is finished instead of waiting until the method handler returns. (#​7998)
  • Special Thanks: @​lqs

Documentation

• examples/features/gracefulstop: add example to demonstrate server graceful stop. (#​7865)

v1.69.4: Release 1.69.4

Compare Source

Bug Fixes

• rbac: fix support for :path header matchers, which would previously never successfully match (#​7965).

Documentation

• examples/features/csm_observability: update example client and server to use the helloworld service instead of echo service (#​7945).

v1.69.2: Release 1.69.2

Compare Source

Bug Fixes

• stats/experimental: add type aliases for symbols (Metrics/etc) that were moved to the stats package (#​7929).
• client: set user-agent string to the correct version.

v1.69.0: Release 1.69.0

Compare Source

Known Issues

• The recently added grpc.NewClient function is incompatible with forward proxies, because it resolves the target hostname on the client instead of passing the hostname to the proxy. A fix is expected to be a part of grpc-go v1.70. (#​7556)

New Features

• stats/opentelemetry: Introduce new APIs to enable OpenTelemetry instrumentation for metrics on servers and clients (#​7874)
• xdsclient: add support to fallback to lower priority servers when higher priority ones are down (#​7701)
• dns: Add support for link local IPv6 addresses (#​7889)
• The new experimental pickfirst LB policy (disabled by default) supports Happy Eyeballs, interleaving IPv4 and IPv6 address as described in RFC-8305 section 4, to attempt connections to multiple backends concurrently. The experimental pickfirst policy can be enabled by setting the environment variable GRPC_EXPERIMENTAL_ENABLE_NEW_PICK_FIRST to true. (#​7725, #​7742)
• balancer/pickfirst: Emit metrics from the pick_first load balancing policy (#​7839)
• grpc: export MethodHandler, which is the type of an already-exported field in MethodDesc (#​7796)
  • Special Thanks: @​mohdjishin

Bug Fixes

• credentials/google: set scope for application default credentials (#​7887)
  • Special Thanks: @​halvards
• xds: fix edge-case issues where some clients or servers would not initialize correctly or would not receive errors when resources are invalid or unavailable if another channel or server with the same target was already in use . (#​7851, #​7853)
• examples: fix the debugging example, which was broken by a recent change (#​7833)

Behavior Changes

• client: update retry attempt backoff to apply jitter per updates to gRFC A6. (#​7869)
  • Special Thanks: @​isgj
• balancer/weightedroundrobin: use the pick_first LB policy to manage connections (#​7826)

API Changes

• balancer: An internal method is added to the balancer.SubConn interface to force implementors to embed a delegate implementation. This requirement is present in the interface documentation, but wasn't enforced earlier. (#​7840)

Performance Improvements

• mem: implement a ReadAll() method for more efficient io.Reader consumption (#​7653)
  • Special Thanks: @​ash2k
• mem: use slice capacity instead of length to determine whether to pool buffers or directly allocate them (#​7702)
  • Special Thanks: @​PapaCharlie

Documentation

• examples/csm_observability: Add xDS Credentials and switch server to be xDS enabled (#​7875)

v1.68.2: Release 1.68.2

Compare Source

Dependencies

• Remove the experimental stats/opentelemetry module and instead add the experimental packages it contains directly into the main google.golang.org/grpc module (#​7936)

v1.68.1: Release 1.68.1

Compare Source

Bug Fixes

• credentials/alts: avoid SRV and TXT lookups for handshaker service to work around hangs caused by buggy versions of systemd-resolved. (#​7861)

Dependencies

• Relax minimum Go version requirement from go1.22.7 to go1.22. (#​7831)

v1.68.0: Release 1.68.0

Compare Source

Known Issues

• The recently added grpc.NewClient function is incompatible with forward proxies, because it resolves the target hostname on the client instead of passing the hostname to the proxy. This bug has been present since the introduction of NewClient. A fix is expected to be a part of grpc-go v1.70. (#​7556)

---

Behavior Changes

• stats/opentelemetry/csm: Get mesh_id local label from "CSM_MESH_ID" environment variable, rather than parsing from bootstrap file (#​7740)
• orca (experimental): if using an ORCA listener, it must now be registered only on a READY SubConn, and the listener will automatically be stopped when the connection is lost. (#​7663)
• client: ClientConn.Close() now closes transports simultaneously and waits for transports to be closed before returning. (#​7666)
• credentials: TLS credentials created via NewTLS that use tls.Config.GetConfigForClient will now have CipherSuites, supported TLS versions and ALPN configured automatically. These were previously only set for configs not using the GetConfigForClient option. (#​7709)

Bug Fixes

• transport: prevent deadlock in client transport shutdown when writing the GOAWAY frame hangs. (#​7662)
• mem: reuse buffers more accurately by using slice capacity instead of length (#​7702)
  • Special Thanks: @​PapaCharlie
• status: Fix regression caused by #​6919 in status.Details() causing it to return a wrapped type when getting proto messages generated with protoc-gen-go < v1. (#​7724)

Dependencies

• Bump minimum supported Go version to go1.22.7. (#​7624)

v1.67.3: Release 1.67.3

Compare Source

Dependencies

• Remove the experimental stats/opentelemetry module and instead add the experimental packages it contains directly into the main google.golang.org/grpc module (#​7935)

v1.67.2: Release 1.67.2

Compare Source

Bug Fixes

• credentials/alts: avoid SRV and TXT lookups for handshaker service to work around hangs caused by buggy versions of systemd-resolved. (#​7861)

v1.67.1: Release 1.67.1

Compare Source

Bug Fixes

• transport: Fix a bug causing stream failures due to miscalculation of the flow control window in both clients and servers. (#​7667)
• xds/server: Fix xDS Server memory leak. (#​7681)

v1.67.0: Release 1.67.0

Compare Source

Bug Fixes

• ringhash: when used with multiple EDS priorities, fix bug that could prevent a higher priority from recovering from transient failure. (#​7364)
  • Special Thanks: @​atollena

Behavior Changes

• In accordance with RFC 7540, clients and servers will now reject TLS connections that don't support ALPN. This can be disabled by setting the environment variable GRPC_ENFORCE_ALPN_ENABLED to false (case insensitive). Please file a bug if you encounter any issues with this behavior. The environment variable to revert this behavior will be removed in an upcoming release. (#​7535)

v1.66.3: Release 1.66.3

Compare Source

Bug Fixes

• transport: Fix a bug causing stream failures due to miscalculation of the flow control window in both clients and servers. (#​7667)
• xds/server: Fix xDS Server memory leak. (#​7681)

v1.66.2: Release 1.66.2

Compare Source

Dependencies

• Remove unintentional dependency on the testing package (#​7579)
• Remove unintentional dependency on the flate package (#​7595)
  • Special Thanks: @​ash2k

Bug Fixes

• client: fix a bug that prevented memory reuse after handling unary RPCs (#​7571)
  • Special Thanks: @​coxley

kubernetes/api (k8s.io/api)

v0.32.2

Compare Source

v0.32.1

Compare Source

v0.32.0

Compare Source

v0.31.6

Compare Source

v0.31.5

Compare Source

v0.31.4

Compare Source

v0.31.3

Compare Source

v0.31.2

Compare Source

v0.31.1

Compare Source

kubernetes/apimachinery (k8s.io/apimachinery)

v0.32.2

Compare Source

v0.32.1

Compare Source

v0.32.0

Compare Source

v0.31.6

[Compare Source](https://redirect.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.