Merged
Conversation
Amp-Thread-ID: https://ampcode.com/threads/T-019d8d6c-2fca-7492-a131-a9d485d7369f Co-authored-by: Amp <amp@ampcode.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
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
0.0.13release publish from currentmainafter the workflow migration tosetup-gradlegradle.propertiesback from0.0.14-SNAPSHOTto0.0.13so thepublish-releasejob runs on merge0.0.13tag, GitHub release, changelog entry, and README update already existTesting
./gradlew assemble check --no-daemon --stacktracegit diff --checkNotes
0.0.13release workflow failed repeatedly in the Gradle wrapper validation step before any build or publish step ran0.0.13artifact under the updated workflow that now usesgradle/actions/setup-gradle