Download Latest Version 0.42.66 source code.zip (8.3 MB) Google Add to Preferred Sources
Home / 0.42.65
Name Modified Size InfoDownloads / Week
Parent folder
0.42.65 source code.tar.gz 2026-07-22 4.8 MB
0.42.65 source code.zip 2026-07-22 8.3 MB
README.md 2026-07-22 8.2 kB
Totals: 3 Items   13.1 MB 0

This is a minor maintenance release appropriate for all ServiceTalk users. This release contains a larger than usual number of behavior changes — please review that section carefully before upgrading.

Changes

Behavior Changes

  • https://github.com/apple/servicetalk/commit/e59e0f94347939ba056dd44ace99fe934aaf8eec - gRPC, HTTP, length-prefixed serializers: new inbound size limits for gRPC messages, aggregated HTTP payloads, and streaming length-prefixed serializer frames (4 MiB defaults) ship warn-only: oversized messages are delivered with a rate-limited log warning (naming the largest exceeding size and the owning client/server) rather than rejected (#3520, [#3564], [#3563], [#3576], [#3579]). Opt into enforcement for:
  • gRPC via maxInboundMessageSize(int) on GrpcClientBuilder/GrpcServerBuilder or
    • io.servicetalk.grpc.netty.temporaryDefaultMaxInboundMessageSize temporary system property;
  • HTTP via maxAggregatedPayloadSize(int) on SingleAddressHttpClientBuilder/HttpServerBuilder or
    • io.servicetalk.http.netty.temporaryDefaultMaxAggregatedPayloadSize temporary system property;
  • FixedLengthStreamingSerializer/VarIntLengthStreamingSerializer via new 3-arg constructors or
    • io.servicetalk.serializer.utils.temporaryDefaultMaxMessageSize temporary system property;
  • https://github.com/apple/servicetalk/commit/e6ae35e84a6e0acb23493f86bc02325b0d2611e2 - http-api: HTTP header values are now validated by default, matching existing header-name validation (#3528).
  • Roll back via io.servicetalk.http.api.temporaryDefaultValidateHeaderValues=false temporary system property;
  • https://github.com/apple/servicetalk/commit/bfcdc784391284a461c21c5813edd315f2e707d1 - buffer-api: ReadOnlyBufferAllocators.wrap(byte[], int, int) / wrap(ByteBuffer) now normalize the returned Buffer's coordinates to start at index 0; callers indexing off the original ByteBuffer's absolute position must update their offsets (#3560)

Security Fixes

New Features

Bug Fixes

Improvements

Dependencies


Thank you

Every idea, review, and bug-report counts and so we thought it is worth mentioning those who helped in this area. Please report any unintended omission.

@bryce-anderson @chrisvest @colestanfield @miroswan @idelpivnitskiy @igavrysh @daschl @fallintoplace @Nadav0077 @LeSingh1

Source: README.md, updated 2026-07-22