Skip to content

Add CI workflow: build, instrumented tests, JitPack release - #15

Merged
ivnbogdan merged 1 commit into
mainfrom
ci/github-actions
Oct 10, 2026
Merged

ivnbogdan merged 1 commit into
mainfrom
ci/github-actions

Conversation

@ivnbogdan

Copy link
Copy Markdown
Contributor

Summary

Adds .github/workflows/ci.yml, triggered on pull requests and on pushes to main.

Job What it does
build ./gradlew build (assemble both modules, lint, unit tests), then publishToMavenLocal to 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.
instrumented Boots an x86_64 API 34 emulator (KVM enabled), builds and installs the example app and the library test APK, and runs connectedDebugAndroidTest. Matrix over api-level so more levels can be added later.
release (main only) Reads the version from aptabase/build.gradle. If no git tag exists for it, creates the tag and a GitHub release using the matching CHANGELOG.md section, 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

  • The existing publish.yml (manual Sonatype publish) is untouched; it has never been run and can be removed separately.
  • Merging this PR will not create a release: 0.0.9 is already tagged, so the release job is a no-op until the next version bump lands on main.
  • The build job's Gradle commands were verified locally against the current main toolchain (AGP 8.4.0, Gradle 8.7, JDK 17).

🤖 Generated with Claude Code

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>
@ivnbogdan
ivnbogdan merged commit 10787a6 into main Oct 10, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant