Closed linghengqian closed 1 year ago
@fniephaus this could be solved if the following would be supported:
- uses: graalvm/setup-graalvm@v1
with:
version: 'dev'
java-version: 'dev'
Thanks for raising this issue, @linghengqian.
setup-graalvm
should have logic to try to use previous dev builds of GraalVM CE
That won't solve your issue because GraalVM dev builds are volatile and will be removed at some point. So even if you see an older JDK17 dev build, it will no longer be available after a few days/weeks and then your builds will start failing.
this could be solved if the following would be supported:
Yes, I think we can support java-version: dev
, although it may still break your builds if your codebase doesn't support building against the latest Java version.
Please take a look at #31, @linghengqian and @alvarosanchez.
Please take a look at #31, @linghengqian and @alvarosanchez.
LGTM!
GraalVM dev build for Java 17
as normal. Github Actions pops up the following Log.setup-graalvm
should have logic to try to use previousdev builds of GraalVM CE
, instead of always pointing to thelatest GraalVM CE dev build
, so that when thedev build of GraalVM CE
only releasesJDK 19
products,setup-graalvm
users can still use the previousJDK 17 dev build
products normally.