15 hours ago
Activiti
1 days ago
grpc-java

V1.84.0

In this release we drop support for Android API level 23 or lower (Marshmallow or earlier), following Google Play Service’s now requiring a minimum of API level 24 (Android 7.0 Nougat).

API Changes

  • xds: Supports injecting custom LDS Resource Name Resolvers (#12925) (ac02c6f37)
  • xds: Add support for creating XdsServerBuilder with SocketAddresses (#12925) (ac02c6f37)
  • api: Add a Supplier overload to Context (#12935) (696653600)

Behavior Changes

  • core: update SPIFFE certificate extraction to comply with X509-SVID spec (#12961) (96807d898)
    Ignore all but the first certificate if the x5c JWK parameter contains multiple values.
    Skip the JWK entry instead of stopping execution or throwing when x5c is missing or contains an empty list, complying with the requirement that entries without x5c must be ignored.

Bug Fixes

  • core: reference-count shared transport factory for OOB channels (#12985) (72c6e5f91)
    Fixes a bug whereby an OOB channel shutdown incorrectly shut down the shared transport factory with the main channel, and the main channel was unable to create subchannels anymore and faced an exception in doing so.
  • xds: Fix shutdownNow() becoming a no-op after shutdown() (#12982) (3cb700719)
  • xds: Add Http11ProxyUpstreamTransport to MessagePrinter (#12971) (d49a589f4)
  • core, xds: Append child channel configurators instead of overwriting (#12921) (296c007c1) Chains multiple childChannelConfigurator() calls instead of overwriting them in ManagedChannelImplBuilder and XdsServerBuilder, ensuring all configurators are preserved and executed when child channels are created.
  • rls: Implement stale_header_data caching and propagation in RLS (#12972) (7843bd437) Caches header_data received in RouteLookupResponse and sends it back as stale_header_data in RouteLookupRequest when refreshing stale cache entries, complying with the RLS specification.

Improvements

  • netty: Fix client-initiated stream limit bypass in NettyServerHandler (#12933) (56205f91c) Configure max active streams limit directly upon DefaultHttp2Connection initialization. Because NettyServerHandler instantiates DefaultHttp2Connection directly rather than using Netty's AbstractHttp2ConnectionHandlerBuilder, it missed Netty's built-in CVE-2026-47244 patch. This left a pre-handshake window where the server's local connection allowed up to Integer.MAX_VALUE active client-initiated streams until a SETTINGS_ACK was received. Enforcing the limit proactively at startup closes this vulnerability window and prevents client-initiated stream floods / resource exhaustion.
  • servlet: AsyncServletOutputStreamWriter detect and handle write when not ready (#12732) (46f308051) In highly concurrent scenarios, cached servlet container ready to write state can become stale. The servlet container may have already transitioned to a 'not ready' state, but the corresponding callback has not yet updated gRPC's internal state. This fix makes the ready state to be evaluated explicitly before attempting to write directly to the servlet output stream.
  • okhttp: Move connection window update before stream termination logic (#12990) (0f859c3bb) By RFC 9113, section 6.9, receivers must take frames into account for flow control even if they're errored. This change moves the stream error response logic after connection window updates
  • core: Coalesce Contiguous Small Buffers for ReadableBuffer to prevent OOM (#12924) (0585d481a)
  • s2a: Default to Post Quantum Cryptography key exchange group (#12894) (bc01994b7)
  • binder: Let servers load their SecurityPolicy asynchronously (9fdef96dc)
  • binder: normalize failed auth future status message (9ffa1e1b7)

Dependencies

  • compiler: Update maximum supported edition to EDITION_2026 (#12945) (6ccd0658e). Update the maximum supported edition in the Java gRPC compiler plugin to EDITION_2026 when compiling against Protobuf version 7.35.0 (v35.0) or later.
  • api: Bump Context to JDK 8 (5d0a012fa)
  • netty: Upgrade Netty to 4.2.16 and netty-tcnative to 2.0.81 (#12969) (1bc2f5a34)

Documentation

  • api: Better explain the executors and how to configure them (ee08f5337)

New Features

  • core, opentelemetry: Implement LB Delay Observability (Proposal A121) (#12807) (073fd5ea1) Implements attempt-level RPC delay observability across the core delayed transport, built-in load balancers (pick_first, round_robin), RLS, and xDS policies, aligned with gRFC A121. Adds LoadBalancer.PickResult.withNoResult(delayType, delayReason) and delay tracing callbacks on ClientStreamTracer. Records attempt delay duration metrics (grpc.client.attempt.delay.duration) and child tracing spans ("Attempt Delay") via the OpenTelemetry plugin.

Thanks to

@Zhengcy05 @carl-mastrangelo @themechbro @JasonLunn @martinbaillie @eado @TimurRakhmatullin86

1 days ago
jedis

8.1.0-beta1

Jedis 8.1.0-beta1 is the first pre-release of the upcoming 8.1.0, introducing support for Smart Client Handoffs (SCH) (#4668).

Smart client handoffs is a feature of Redis Cloud and Redis Software that notifies clients about planned maintenance shortly before it happens, so the client can respond gracefully instead of hitting command timeouts and dropped connections. Jedis reacts with relaxed timeouts and pre-handoffs. SCH requires RESP3 and is enabled automatically on RESP3 connections; see the Jedis SCH guide for configuration options.

This is a pre-release: APIs introduced here may change before 8.1.0 GA.

Changes

🚀 New Features

  • Smart Client Handoffs (SCH): maintenance notifications support (#4668)

🐛 Bug Fixes

  • Do not deliver pub/sub push messages as replies outside an active subscription (#4701)
  • Refresh primaryNodesCache in JedisClusterInfoCache.discoverClusterSlots (#4692)
  • Accept null VAddParams in vaddFP32 with reduceDim (#4684)
  • Fix TSAddParams emitting DUPLICATE_POLICY twice (#4683)
  • Register source keys via key() in zrangestore, geosearchStore, eval (#4675)

🧰 Maintenance

  • [scenario tests stability] Pipeline ClusterTopologyRefreshIT verification to fit the test timeout (#4713)
  • Bump redis-authx dependencies 1.0.1-beta2 -> version 0.2.0 (#4712)
  • Stabilize integration tests against auth-required, high-latency environments (#4700)
  • chore(deps): bump org.json:json from 20260719 to 20260814 (#4699)
  • chore(deps-dev): bump jackson.version from 2.22.1 to 2.22.2 (#4698)
  • Add nightly test-metrics workflow (#4689)
  • chore(deps-dev): bump com.kohlschutter.junixsocket:junixsocket-core from 2.10.1 to 2.11.0 (#4687)
  • Start release notes for 8.1.0 (#4681)
  • Bump snapshot version to 8.1.0 (#4680)
  • chore(deps-dev): bump org.apache.httpcomponents.client5:httpclient5-fluent from 5.6.3 to 5.6.4 (#4678)

Contributors

We'd like to thank all the contributors who worked on this release!

@HDPark95, @atakavci, @bobymicroby, @dependabot[bot], @ggivo, @insaf021, @kalayciburak, @uglide

Full Changelog: https://github.com/redis/jedis/compare/v8.0.0...v8.1.0-beta1

1 days ago
spring-cloud-tencent

2.1.2.0-2025.1.1

Dependency Version

  • Spring Cloud Tencent: 2.1.2.0-2025.1.1
  • Spring Cloud: 2025.1.1
  • Spring Boot: 4.0.2
  • Spring Framework: 7.0.3

Features / Enhancements

Upgrade to Spring Cloud 2025.1.x from branch 2024.

Contributors

Thanks to the contributors who participated in this release!

@SkyeBeFreeman

How to upgrade

This version is compatible version from the previous corresponding version, so just upgrade spring-cloud-tencent-dependencies version to it. If you need to change the Spring Cloud version, please refer to the documentation Release Note to modify other related dependent versions synchronously.