Skip to content

Automate Android Maven Central publishing on release#146

Merged
petewarden merged 1 commit intomoonshine-ai:mainfrom
sanogueralorenzo:msanoguera/publish_android
Mar 16, 2026
Merged

Automate Android Maven Central publishing on release#146
petewarden merged 1 commit intomoonshine-ai:mainfrom
sanogueralorenzo:msanoguera/publish_android

Conversation

@sanogueralorenzo
Copy link
Contributor

@sanogueralorenzo sanogueralorenzo commented Mar 9, 2026

Summary

  • add a GitHub Actions workflow to publish Android artifacts to Maven Central on each published GitHub Release
  • validate that release tag version (e.g. v0.0.50) matches moonshine-voice version in build.gradle.kts before publishing
  • align scripts/publish-android.sh with the explicit publishAndReleaseToMavenCentral task

Why

v0.0.49 exists as a GitHub release, but ai.moonshine:moonshine-voice:0.0.49 is not available from Maven Central, so downstream Android projects cannot resolve it.

Notes

This workflow expects the following repository secrets:

  • MAVEN_CENTRAL_USERNAME
  • MAVEN_CENTRAL_PASSWORD
  • SIGNING_KEY
  • SIGNING_KEY_PASSWORD

@petewarden petewarden merged commit 6ead1a6 into moonshine-ai:main Mar 16, 2026
@petewarden
Copy link
Contributor

Thanks @sanogueralorenzo ! I'll re-run the release process soon, so the Maven artifact is correctly updated.

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