Maybe we should do an intermediate step where the minimum version is Java 11 but we use Java 17 as base image? That way we can give a heads-up in the next release for users running Kroki from the jar file. What do you think?

Maybe we should do an intermediate step where the minimum version is Java 11 but we use Java 17 as base image? That way we can give a heads-up in the next release for users running Kroki from the jar file. What do you think?

@ggrossetie, sounds good, done! I changed the PR title to reflect this as well.

From my side this is good to merge now. I can't run the tests locally though¹ (neither on this branch nor on main), can you trigger the CI tests to run on this branch? On the previous runs it looked like only the "test-container" checks ran, not the other CI pipelines. (Or just merge if things look fine to you.)

¹ A few tests generate differing SVG output with slightly different floating point results. I suspect somehow my versions are not matching up, but I couldn't figure out what's different. I am running node 18.18.2, which seems to be what generates the differences in some tests. But as this happens on main as well I suspect it's just my setup that is different.

¹ A few tests generate differing SVG output with slightly different floating point results. I suspect somehow my versions are not matching up, but I couldn't figure out what's different. I am running node 18.18.2, which seems to be what generates the differences in some tests. But as this happens on main as well I suspect it's just my setup that is different.

It can be related to your operating system and/or fonts. I will run the tests on the CI.

Thanks!