Fix Maven publish workflow + bump CI actions#31
Merged
Conversation
PublishMaven.yml was failing with `sbt: command not found` because the ubuntu-latest runner image no longer ships sbt preinstalled. Add `sbt/setup-sbt@v1` to match Build.yml. Also bump action versions in both workflows to silence the Node.js 20 deprecation warnings: - actions/checkout v4 -> v6 - actions/setup-java v4 -> v5 - actions/setup-node v4 -> v6 PublishMaven.yml: Java 8 -> 11 (matches apex-parser publish), Node 16 -> 22. Output bytecode target stays Java 8 via build.sbt javacOptions.
nawforce
approved these changes
May 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
PublishMaven.ymlwas failing withsbt: command not found— theubuntu-latestrunner image no longer ships sbt preinstalled. Addsbt/setup-sbt@v1to matchBuild.yml.actions/checkoutv4 → v6,actions/setup-javav4 → v5,actions/setup-nodev4 → v6.PublishMaven.yml: Java 8 → 11 (matches the apex-parser publish workflow), Node 16 → 22. Bytecode target stays Java 8 via the-source 8 -target 8javacOptionsinbuild.sbt.Test plan
v2.0.0-beta.1tag (or whatever tag you cut) and confirmsbt ci-releaseruns to completion