Fix Maven Central publish workflow: use JDK 17#43
Closed
winrid wants to merge 1 commit into
Closed
Conversation
AGP 8.9 and the Spotless plugin both require a JDK 17+ runtime, but the publish workflow ran on JDK 11, so it failed at configuration time (the last few releases never actually published). Bump the workflow JDK to 17.
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.
Problem
The
Publish Android SDK to Maven Centralworkflow has been failing on every release since v1.0.0. It runs on JDK 11, but:So the build failed during project configuration and nothing was ever published for v1.0.0, v1.1.0, or v2.0.0.
Fix
Bump the workflow's JDK from 11 to 17.
Follow-up
Once merged, the
v2.0.0tag needs to be re-pointed to a commit that includes this fix so the release actually publishes to Maven Central.