Skip to content

Add GitHub Actions CI and release workflows - #1

Merged
KennyYe merged 1 commit into
mainfrom
cursor/github-actions-ci-37ff
Oct 9, 2026
Merged

KennyYe merged 1 commit into
mainfrom
cursor/github-actions-ci-37ff

Conversation

@KennyYe

@KennyYe KennyYe commented Oct 9, 2026

Copy link
Copy Markdown
Collaborator

Adds CI for PRs and main, plus a tag-driven release path that keeps JitPack as the primary publish target.

What changed

  • CI (.github/workflows/ci.yml): on every PR and push to main, run assembleRelease, unit tests, ktlint, and Android Lint. Actions pinned to current Node 24 majors (checkout@v7, setup-java@v5, setup-android@v4).
  • Release (.github/workflows/release.yml): on semver tags, re-run the same checks, create a GitHub Release, and request a JitPack build for the tag. Maven Central publish job is present but disabled (if: false) until secrets are configured.
  • ktlint with a minimal .editorconfig so the current tree passes; formatting-only touch-ups in TapAppLink.kt.
  • Unit tests for configure / reset / environment / offer fields (none existed before).
  • README: local check command, JitPack release notes, and the one-time Maven Central secrets setup for a repo admin.

Out of scope

No SDK behaviour changes (Play Install Referrer and persistence stay for a later PR).

Verify

./gradlew assembleRelease test ktlintCheck lintRelease
Open in Web Open in Cursor 

Run assemble, unit tests, ktlint, and Android Lint on PRs and main.
On semver tags, re-run checks, create a GitHub Release, and request a
JitPack build. Leave Maven Central publish disabled behind secrets and
document the one-time admin setup in the README.

Co-authored-by: Kenny Ye <KennyYe@users.noreply.github.com>
@KennyYe
KennyYe marked this pull request as ready for review October 9, 2026 13:16
@KennyYe
KennyYe merged commit b3dfade into main Oct 9, 2026
1 check 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.

2 participants