setup-java@v4 setup for sbt failing on Linux with sbt: command not found

[dnkanga]

Description:
This seemingly broke overnight, i'm attempting to setup the build with this

jobs:
  unit-test-with-coverage:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v2
      - name: Set up JDK 11
        uses: actions/setup-java@v4
        with:
          java-version: '11'
          distribution: 'adopt'

      - name: Compile and run tests
        run: sbt clean coverage test coverageReport

and the build is failing with

Run sbt clean coverage test coverageReport
  sbt clean coverage test coverageReport
  shell: /usr/bin/bash -e {0}
  env:
    GITHUB_TOKEN: ***
    ORG_TOKEN: ***
    JAVA_HOME: /opt/hostedtoolcache/Java_Adopt_jdk/11.0.24-8/x64
    JAVA_HOME_11_X64: /opt/hostedtoolcache/Java_Adopt_jdk/11.0.24-8/x64
/home/runner/work/_temp/b7c25d22-b1b1-4c67-b34a-c29a4ed01426.sh: line 1: sbt: command not found
Error: Process completed with exit code 127.

Platform:

• [ X] Ubuntu
• macOS
• Windows

Runner type:

• [ X] Hosted
• Self-hosted

[marvinborner]

I also have this issue. This is likely because of the ubuntu-latest update which no longer includes sbt by default.

Also using the sbt/setup-sbt action fixes it.

[dnkanga]

@tjmw when will the fix for this be rolled out?

[aparnajyothi-y]

Hello Everyone,

Thank you for creating this issue. There is already an issue raised under runner-images. Here are my findings:

• Previously, the ubuntu-latest tag was associated with the ubuntu-22.04 image. It is now associated with the ubuntu-24.04 image.
• If you use the ubuntu-22.04 version and run the pipeline, it should work.

For further updates or fixes, please track issues #10767 and #10636.

Feel free to reach out if you need any clarifications.

[aparnajyothi-y]

Hello @dnkanga, please let us know if the information provided above resolved your issue? If you have any further concerns or questions, feel free to reach out.

[aparnajyothi-y]

Hello @dnkanga, just gently following up to see if the information provided above has resolved your issue. If you have any further questions or concerns, please don’t hesitate to reach out.

[aparnajyothi-y]

Hello @dnkanga, We are proceeding to close this issue after two reminders as we didn't hear anything from you for a long time.
Please feel free to reach us in case of any further concerns to reopen this issue.