Was there a reason the Kermit JVM source compatibility needed to be bumped to 17 in 2.0.0? My library has compatibility at 1.8, which this change breaks.
09/21/2023, 11:06 PM
I will ask internally. I would imagine that decision was during the Java version updates across the board.
09/21/2023, 11:11 PM
I see the JVM version was bumped on the runners. Seems the source compatibility would only need to be changed if newer language features were needed though. Maybe it just needed an explicit compatibility declaration, where it didn't before though. Only the samples had 1.8 explicit before.
Nice having the linuxArm64 target now though.
I tested reverting source compatibility to 1.8 and checks passed successfully. I made a PR.