Fix release_40x workflow: Central Portal + sbt install - #914
Open
sksamuel wants to merge 1 commit into
Open
Conversation
This workflow lives on master but releases the 4.0.x line. After #913 wired release publishing on release/4.0.x through sbt's localStaging, plain publishSigned writes only to a local dir and never reaches Sonatype — the upload/release step has to invoke sonaUpload/sonaRelease explicitly. The scala-2_13 job was also still on actions/setup-java@v1 with no sbt installed (exit 127). Mirror release.yml on release/4.0.x: single job, sbt installed via coursier, and `sbt +publishSigned sonaUpload sonaRelease` to crossbuild both Scala versions into one Central Portal deployment bundle. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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
The user-dispatched
release_40xworkflow (which lives on master and releases the 4.0.x line) failed on the scala-2_13 job with exit 127 —sbt: command not found(run 25775857651).Two problems were stacked:
scala-2_13job still usedactions/setup-java@v1(no sbt). Thescala-2_12job had already been migrated tocoursier/setup-action, but the second job was overlooked.sbt ++<ver> publishSignedno longer reaches Sonatype: PR Release publishing via Sonatype Central Portal #913 routed releasepublishToon therelease/4.0.xbranch through sbt'slocalStaging, sopublishSignednow writes only to a local staging dir. The upload+release step has to invokesonaUpload/sonaReleaseexplicitly.Mirror the structure of
release.ymlonrelease/4.0.x(from #913):releasejob (the two parallel jobs would race onsonaReleaseand produce competing Central Portal deployments).coursier/setup-action@v1.sbt +publishSigned sonaUpload sonaRelease—+publishSignedcrossbuilds 2.12.14 + 2.13.17 fromcrossScalaVersionsinto a single local staging bundle, then upload + release once.Test plan
release_40xagainstrelease/4.0.xwith a dry-run version; verify a single deployment appears at https://central.sonatype.com/publishing/deployments and is released.🤖 Generated with Claude Code