v1.9.4

MaxContentLength for Netty

All Netty backends now support restricting maximum request body length. This per-endpoint protection ensures that no more bytes are loaded from body than given limit. Exceeding the limit results in HTTP 413 Payload Too Large response. For details see https://tapir.softwaremill.com/en/latest/endpoint/security.html#limiting-request-body-length for details.
More backends will support this feature in upcoming versions.

• If you have been using the global NettyConfig.maxContentLength setting, it's no longer available. Please switch to the new per-endpoint annotation.
• NettyConfig.defaultNoStreaming has been removed, use NettyConfig.default

Removed ZIO 1.x modules

Tapir integrations for zio, zio-json, zio-http, etc. are now available only for ZIO 2.x

What’s Changed

• Remove test leftovers (#3370) @kciesielski
• Remove zio1 support (#3369) @kciesielski
• Adjust Play 2.9 to changes in RequestBody (#3368) @kciesielski
• MaxContentLength support for Netty pt 2 (#3337) @kciesielski
• Update pekko-discovery, pekko-slf4j, ... to 1.0.2 (#3363) @softwaremill-ci
• separated test report (#3351) @micsza
• Fix automerge - use squash method. (#3358) @micsza
• use-repo-token-for-rebase-cmd-dispatch (#3353) @micsza

Dependency updates

• Update json4s-core, json4s-jackson to 4.0.7 (#3365) @softwaremill-ci
• Update swagger-ui to 5.10.3 (#3364) @softwaremill-ci
• Update jsoniter-scala-core, ... to 2.25.0 (#3362) @softwaremill-ci
• Update logback-classic to 1.4.14 (#3361) @softwaremill-ci
• Update zio-http to 3.0.0-RC4 (#3357) @softwaremill-ci