Repository navigation
ci: test pull requests and release to Maven Central on version tags - #41
Merged
Merged
Conversation
Publishing moves to com.vanniktech.maven.publish 0.34.0 with Central Portal auto-release and in-memory signing in CI; the artifact (aar, sources, module, POM) matches the old maven-push.gradle output. CI runs the unit tests and the release build on pull requests and pushes to master. Pushing a tag X.Y.Z checks it against VERSION_NAME, runs the tests, publishes and releases to Maven Central, waits for the POM on repo1 and creates the GitHub release from the CHANGELOG. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
19.0.0 is not published yet, so the Unreleased entry joins its section. Co-Authored-By: Claude Opus 5.5 <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
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.
Automates Android releases. Push the tag
X.Y.Zand GitHub Actions publishes and releases to Maven Central. The manual Central Portal step is gone.maven-push.gradleis replaced bycom.vanniktech.maven.publish0.34.0 (the newest version that works with Gradle 8.10.2 / AGP 8.8), set to auto-release and sign all publications.publishToMavenLocal: same files as 18.1.0 (aar, sources, module, pom,.asc, no javadoc).POM_INCEPTION_YEARremoved (unused; the plugin would have added it to the POM).ci.yml(pull requests and pushes tomaster)::gleap:testDebugUnitTest :gleap:assembleReleaseon JDK 17.release.yml(tagX.Y.Z, plus aworkflow_dispatchdry run that publishes to Maven Local with real signing):VERSION_NAME, that the tag is on master, and that the version isn't on Central yet;publishAndReleaseToMavenCentral;Secrets:
MAVEN_CENTRAL_USERNAME,MAVEN_CENTRAL_PASSWORD,SIGNING_KEY(ASCII-armored),SIGNING_KEY_ID(short id),SIGNING_KEY_PASSWORD.Local publishing:
~/.gradle/gradle.propertiesneedsmavenCentralUsername/mavenCentralPassword(same values asNEXUS_*). Thesigning.*keys work unchanged.Before tagging 19.0.0:
io.gleap:gleap-okhttp-interceptor:19.0.0(Release 19.0.0 as an empty artifact and deprecate in favour of the interceptor built into Android SDK 19.0.0 OKHttpInterceptor#2). The SDK constraint pins it, and it isn't on Central yet.## UnreleasedCHANGELOG section (authenticated files) sits above## 19.0.0. Release it as its own version or fold it into 19.0.0.Verification: 180/180 unit tests pass, actionlint is clean, and the CI in-memory signing path was checked with a throwaway key. A real upload hasn't been tested yet; the first one should be the
workflow_dispatchdry run once the secrets are set.🤖 Generated with Claude Code