Repository navigation
Add CI workflow: build, instrumented tests, JitPack release - #15
Merged
Merged
Conversation
Runs on pull requests and on pushes to main. - build: ./gradlew build (assemble, lint, unit tests) followed by publishToMavenLocal to mirror what JitPack runs; uploads the AAR and sample APK, and the reports on failure - instrumented: boots an API 34 emulator, installs the example app and the library test APK and runs connectedDebugAndroidTest - release (main only): reads the version from aptabase/build.gradle; if no tag exists for it yet, creates the tag and GitHub release with the matching CHANGELOG section, then requests the artifact on JitPack to trigger the build and fails if JitPack does not produce the AAR Co-Authored-By: Claude Fable 5.1 <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.
Summary
Adds
.github/workflows/ci.yml, triggered on pull requests and on pushes tomain../gradlew build(assemble both modules, lint, unit tests), thenpublishToMavenLocalto run the same publication JitPack does and verify the AAR/POM exist. Uploads the AAR and sample debug APK as artifacts, and lint/test reports on failure.connectedDebugAndroidTest. Matrix overapi-levelso more levels can be added later.aptabase/build.gradle. If no git tag exists for it, creates the tag and a GitHub release using the matchingCHANGELOG.mdsection, then requests the artifact from JitPack to trigger the build and fails the job if JitPack does not end up serving the AAR. When the version has not been bumped it exits early.Action versions are pinned to current majors:
actions/checkout@v7,actions/setup-java@v6,gradle/actions/setup-gradle@v6,reactivecircus/android-emulator-runner@v2,actions/upload-artifact@v7.Notes
publish.yml(manual Sonatype publish) is untouched; it has never been run and can be removed separately.0.0.9is already tagged, so the release job is a no-op until the next version bump lands onmain.maintoolchain (AGP 8.4.0, Gradle 8.7, JDK 17).🤖 Generated with Claude Code