After some issues with OSSRH’s switch to token bas...
# strikt
r
After some issues with OSSRH’s switch to token based auth, I’ve finally published v0.35.1
🎉 3
🙌 2
K 4
d
Thanks for the new release 🙏. Strikt is my favorite testing framework. I'm building a library that uses Strikt so I'm just curious how you made the decision to remove support for JDK < 17 as I need to make a similar decision. Since Android only started using JDK 17 with Android 14, this seems like it would only support about 25% of the Android marketshare but I'm not sure if this is an unrelated statistic: https://gs.statcounter.com/android-version-market-share Can Android apps use the newest version of Strikt with JDK 17 and still deploy to devices with Android 13 or older? I'm a backend developer so I'm not sure how the Android world works.
r
I’m honestly in the same position. I’ve done a tiny bit of iOS dev but never any android work. I do web front end, but I’m predominantly a back end dev. The decision is pure laziness. I needed to upgrade to 17 for Spring Boot 3 and that is something I personally am far more likely to use than anything that might need an older JVM.