Skip to content

chore: do not require Java 17 for launching Gradle yet#927

Merged
vlsi merged 1 commit intosigstore:mainfrom
vlsi:buildjdk
Mar 11, 2025
Merged

chore: do not require Java 17 for launching Gradle yet#927
vlsi merged 1 commit intosigstore:mainfrom
vlsi:buildjdk

Conversation

@vlsi
Copy link
Collaborator

@vlsi vlsi commented Mar 11, 2025

Summary

We still require Java 17 for javac, however we could be fine if user launches Gradle with Java 8 or Java 11.

So far no plugins seems to require Java 17, so let's ease the requirements.

It should resolve issues with CodeQL autobuild which assumes we need Java 11: https://github.com/sigstore/sigstore-java/actions/runs/13782007549/job/38541785670#step:5:43

An alternative option would be going with manual build, however, I don't have time to investigate it.

Release Note

NONE

Documentation

NONE

We still require Java 17 for javac, however we could be fine if user
launches Gradle with Java 8 or Java 11.

So far no plugins seems to require Java 17, so let's ease the requiremenets

Signed-off-by: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
@vlsi vlsi merged commit 61bf511 into sigstore:main Mar 11, 2025
12 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments