Declarative, type-safe web endpoints library
:warning: Scala Native support temporarily suspended
After the recent release of Scala Native 0.5.1 the Scala ecosystem is adapting and gradually more and more libraries are released with 0.5.1 support, often as the only supported native version. Tapir needed to update some dependencies like sttp-shared, sttp-model and some external dependencies like upickle, which makes it incompatible with scala-native 0.4. Since we can't switch to 0.5 until other dependencies are available, native support is temporarily suspended. We will work on restoring it, starting with core, as soon as transitive dependencies are released. See the description of https://github.com/softwaremill/tapir/pull/3692 for more details.
anyOf schema for oneOfVariants with the same status code and content-type (#3703) @suslikoerrorOutVariantsPrepend should try to match passed variants before falling back to the default one (#3698) @mkubalaDue to issues with Sonatype Central repository, releases 1.10.1 and 1.10.2 failed with incosistent state, so 1.10.3 is the next version number after 1.10.0.
You might notice some changes in your generated schemas - all components will now include a title field, which should fix some rendering issues (more specifically fixing how coproducts are displayed) with newer Swagger UI versions - that's covered in #3593.
Moreover, we're using a new sttp-apispec release (#3604), which includes a small but binary-incompatible change - adding the uniqueItems property, making Sets properly represented in schemas. Not that the incompatibility is only for the sttp-apispec project, it does not affect tapir's core, only the documentation generation module.
uniqueItems property to Set schemas (#3604) @ghikuseHeadTagForObjectNames flag to permit splitting generated endpoint objects by tag (#3594) @hughsimpson