SBT is no longer available on ubuntu-latest image.

[sageserpent-open]

This is an FYI about the upgrade: actions/runner-images#10636.

I've run into this in the CI build for Kinetic Merge (https://github.com/sageserpent-open/kineticMerge) and Americium (https://github.com/sageserpent-open/americium) - the latter uses this project's actions to publish releases.

It seems SBT has been dropped from Ubuntu-24.04; fortunately folks have kindly provided a new action to setup SBT in a workflow: (https://github.com/sbt/setup-sbt).

I've added the following stanza to the CI builds for Kinetic Merge and Americium:

jobs:
  build:

    runs-on: ubuntu-latest

    steps:

      # New stanza....
      - uses: sbt/setup-sbt@v1

That sorts them both out nicely.

I can have a go at this myself when the next Americium release is due by forking this repository and playing around with pushing trial commits to GitHub, but it may be a lot quicker for the maintainers to do. Let me know if you're happy with amateur help. 😄

[rtyley]

Hi @sageserpent-open, thanks for reporting the issue! We've been encountering this issue a fair bit too over the past couple of months across our many different Scala repos, and I thought we had already updated gha-scala-library-release-workflow, but it turns out we'd missed it - we actually updated gha-scala-library-release-workflow for this issue yesterday, with PR #51 - after you raised this issue, but before I'd actually seen it!

It's lovely to hear you've been using the gha-scala-library-release-workflow on sageserpent-open/americium, I can see that it's cut a fair few releases for you. Note that if you want the automated version-compatibility checking functionality (where your major/minor version number is automatically incremented if you make a binary incompatible change), you'll need to add a bit of sbt config:

releaseVersion := ReleaseVersion.fromAggregatedAssessedCompatibilityWithLatestRelease().value

[sageserpent-open]

Nice work, @rtyley - I've cut over to using v1 of gha-scala-library-release-workflow, it is currently building a release of Americium as I type.

The tip about the automatic increment of the release version is appreciated, I'll mull that over.

Yes, I'm a satisfied customer, thanks for the work you and others have done.

I much prefer to have a CI release process than having to release from my local computer with all the secrets kept locally too. Opens up the possibilty for others to trigger releases should Americium turn into a development empire. 😀