Action fails without JDK set

[DominikZig]

It seems this action fails with:

Output project model path does not exist after autobuilder execution: /home/runner/work/_temp/seqra-artifacts/c5b66e8835af89c2884bfc900deead026704a5d8/project
Autobuilder failed to compile the project
Native compilation has failed: all Java resolution attempts failed
there was a problem during the compile step, check the full logs: /tmp/seqra/logs/2026-01-26_10-44-00.log

╭─Suggestions─╮
╰─┬───────────╯
  └── If native compilation fails due to missing required Java, set JAVA_HOME according to the project's requirements or try Docker-based compilation:
      └── seqra compile . --compile-type docker --output /home/runner/work/_temp/seqra-artifacts/c5b66e8835af89c2884bfc900deead026704a5d8/project

Adding uses: actions/setup-java@v4 as an intermediary step to install a JDK seems to fix it. It would be good if this was documented.

[seqradev]

Hi @DominikZig, thanks for reporting this!

I've updated the README to document this requirement. Seqra analyzes compiled bytecode, so the CI environment needs to be configured to compile your project (e.g., setting up JDK via actions/setup-java for Java/Kotlin projects).

If you run into any other issues or have feature requests, please don't hesitate to open an issue — we're happy to help!