Ensure sbt is properly installed in GitHub actions #738
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
Using the Guardian-provided setup-scala workflow allows us to configure and install Java and sbt at the same time. It takes the Java version out of the .tool-versions file, so this file is also added with a (currently) up-to-date Java version.
How to test
We should see the workflows complete successfully now.
How can we measure success?
We'll avoid these workflows breaking when GitHub starts to roll-out the new base image from 5th Dec.
Have we considered potential risks?
We're specifying a needlessly specific Java version in the .tool-versions file, to appease
asdf
. We will separately migrate to just the major version by adopting mise, but this is something to change globally when we are ready.