The latest sttp-apispec depends on circe-yaml 0.15.1 (November 2023), which is pretty far behind (diff) their latest 0.16.0 release (August 2024).
I'd suggest it'd be prudent to try to update. FWIW, I've been running an application for a little while that evicts circe-yaml 0.15.1 for 0.16.0 and it's been fine, so I'm optimistic it shouldn't be a challenge, but I don't know if there are known issues, challenges, or reasons to hold back (if so, perhaps upgrading to 0.15.3 would still be approachable).
(Curiously, I don't see any Scala-steward PRs for this, so I'm wondering if the ignore setting for 1.x.x is misbehaving.)
I did create a fork in which I ran tests (I was also surprised at the 6G testing need when I had heap issues the first time) that passed, updated the circe-yaml version to 0.16.0, and promptly ran into Scala version errors, suggesting that circe-yaml depends on a higher version of Scala 2.13 than sttp-apispec does—I'm not sure if that suggests an increase to that minimum, too, or if that's the reason not to update.
[IJ]asyncapiCirceYaml / evicted
[warn] Scala version was updated by one of library dependencies:
[warn] * org.scala-lang:scala-library:2.13.14 is selected over {2.13.13, 2.13.8, 2.13.11}
[warn] +- com.softwaremill.sttp.apispec:asyncapi-circe-yaml_2.13:0.0.0+1-fe6fd9c2+20250331-0920-SNAPSHOT (depends on 2.13.14)
I'm happy to snag some minutes here and there to work on this if there are tips or reasoning to share with me—I'm new to contributing to softwaremill projects.
The latest sttp-apispec depends on circe-yaml 0.15.1 (November 2023), which is pretty far behind (diff) their latest 0.16.0 release (August 2024).
I'd suggest it'd be prudent to try to update. FWIW, I've been running an application for a little while that evicts circe-yaml 0.15.1 for 0.16.0 and it's been fine, so I'm optimistic it shouldn't be a challenge, but I don't know if there are known issues, challenges, or reasons to hold back (if so, perhaps upgrading to 0.15.3 would still be approachable).
(Curiously, I don't see any Scala-steward PRs for this, so I'm wondering if the ignore setting for 1.x.x is misbehaving.)
I did create a fork in which I ran tests (I was also surprised at the 6G testing need when I had heap issues the first time) that passed, updated the circe-yaml version to 0.16.0, and promptly ran into Scala version errors, suggesting that circe-yaml depends on a higher version of Scala 2.13 than sttp-apispec does—I'm not sure if that suggests an increase to that minimum, too, or if that's the reason not to update.
I'm happy to snag some minutes here and there to work on this if there are tips or reasoning to share with me—I'm new to contributing to softwaremill projects.