Skip to content

Add GitHub Actions CI and npm release publishing - #1

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

KennyYe merged 1 commit into
mainfrom
cursor/add-github-actions-ci-1570

Conversation

@KennyYe

@KennyYe KennyYe commented Oct 9, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Adds CI on every PR and push to main, plus a tag-gated npm publish workflow so we cannot ship a version that does not match package.json.

What runs

CI (PR / main)

  • Typecheck, ESLint, Jest, tsc build, and npm pack --dry-run
  • Android native module compile via a minimal Gradle project under ci/android

Release (v* tags only)

  • Same JS checks, then refuses to publish unless the tag (without the leading v) equals package.json version
  • npm publish --access public --provenance using trusted publishing (OIDC) when configured, with optional NPM_TOKEN fallback

This would have blocked the existing 0.2.0 tag, which still had 0.1.3 in package.json.

Kenny one-time setup

See PUBLISHING.md: configure the npm Trusted Publisher for workflow release.yml, or add an NPM_TOKEN repo secret as fallback.

Status

GitHub Actions CI on this branch: both jobs green (JS checks + Android compile).

Open in Web Open in Cursor 

Run typecheck, lint, Jest, build, pack dry-run, and Android Gradle
compile on PRs and main. Publish from v* tags only when the tag matches
package.json, with OIDC trusted publishing and NPM_TOKEN fallback.

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 35b7369 into main Oct 9, 2026
2 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.

2 participants