What softwaremill/tapir shipped

Codegen now supports OpenAPI 3.1 exclusiveMinimum and exclusiveMaximum, where those fields replace minimum and maximum directly. Scala3 recursive type schema guidelines were also clarified. Dependency updates this week include vertx 5.2.3, sttp client4 4.1.0, netty 4.2.20.Final a

This week codegen gained support for OpenAPI 3.1 exclusiveMinimum and exclusiveMaximum, which in 3.1 directly replace minimum and maximum rather than acting as additional boolean fields. The Scala3 recursive type schema guidelines were also clarified with requirements for caching, along with a request for alternatives to implicit def, which may be deprecated in the future. Dependency updates landed for vertx-codegen and vertx-web 5.2.3, sttp client4 cats and circe 4.1.0, sttp client4 core 4.0.27, jsoniter-scala 2.42.2, opentelemetry-semconv 1.45.0, netty-all 4.2.20.Final, scala-java-time 2.9.0, Guava 33.8.0-jre and logback-classic 1.6.6.

Tapir update: fixed code generation for some unsupported response combinations and migrated to Scala 3.9.0 LTS. Also bumped pekko-http, vertx, OpenTelemetry, sttp-mock-server, swagger-ui and jsoniter-scala.

This week in tapir: code generation was fixed for some unsupported response combinations, including improved handling of optionality-related response cases. The project also migrated to Scala 3.9.0 LTS, with a build note that openapiCodegenCore compiled with sbt 2.0.x needs Scala 3.8 while sbt 2.1.x will use Scala 3.9. Dependency updates include pekko-http 1.4.1, vertx-codegen and vertx-web 5.2.1, OpenTelemetry 1.67.0, sttp-mock-server and related modules 1.13.33, swagger-ui 5.33.1, and jsoniter-scala 2.41.4.

Week's highlights: sbt 2 migration complete, Vert.x cats streaming deadlock fixed, and zio-json eviction issue resolved. Multiple dependency updates improve ecosystem compatibility.

This week brought significant infrastructure improvements to tapir. The sbt 2 migration is now complete, addressing build tooling for modern development. A critical fix resolves Vert.x cats streaming deadlocks that occurred with fixed-size compute pools. We've also resolved dependency conflicts, particularly the zio-json eviction error when combining tapir-zio-http-server with tapir-json-zio. Code generation now supports extended content types with improved centralization. Dependency updates and JDK 17 build support prepare the project for future development.

Tapir v1.13.32 out: Netty 408 response for incomplete requests, fixed OpenTelemetry duplicate metrics, improved enumeration handling, and http4s Blaze→Ember migration.

Tapir v1.13.32 is out with several important fixes. Netty now responds with 408 Request Timeout when timeouts occur before the body is fully received, distinguishing incomplete requests from backend timeouts. OpenTelemetry metrics no longer record duplicate entries. Enumeration schemas properly handle customise annotations, and http4s has migrated from Blaze to Ember for better cross-platform support.

Tapir now builds cleaner with Scala 3 on JVM 25, updated OpenTelemetry to 1.66.0, and refreshed Vert.x and AWS Lambda dependencies.

This week's Tapir updates focus on forward compatibility and dependency freshness. We've added Scala 3 compiler flags for JVM 25 compatibility, upgraded OpenTelemetry to 1.66.0, and refreshed Vert.x and AWS Lambda client libraries. These changes keep the project current with the latest platform capabilities and library improvements.