You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Nobody" uses that old Java these days, I'd expect there to be 21. Tryid to deploy my test throug Cloud Shell and it only allowed to choose between 17 & 21.
The text was updated successfully, but these errors were encountered:
Java 11 is hardcoded, which I really want to bump but that'd be a breaking change to most people. Our next opportunity is with google-24 builder coming later this year when we publish the Ubuntu 24 based builders. We really should just unpin the java buildpack and respect the language-idiomatic declarations
I don't think we need to wait for google-24 to make this change. All other runtimes default to the latest available version and parse framework configs / env vars for overrides. IIRC the reason we didn't do this for Java was because we were pulling the JDK from a public repo that didn't have a version index, but that is no longer an issue now that we are hosting our own JDK tarballs.
"Nobody" uses that old Java these days, I'd expect there to be 21. Tryid to deploy my test throug Cloud Shell and it only allowed to choose between 17 & 21.
The text was updated successfully, but these errors were encountered: