Skip to content

Attach only the APK to GitHub Releases - #126

Merged
Slacker-LLC merged 1 commit into
mainfrom
chore/release-apk-only
Oct 4, 2026
Merged

Slacker-LLC merged 1 commit into
mainfrom
chore/release-apk-only

Conversation

@Slacker-LLC

Copy link
Copy Markdown
Owner

Summary

  • GitHub Releases attach only openIME-v<VERSION>-arm64-release.apk; SHA256SUMS.txt and THIRD_PARTY_NOTICES.release.md are no longer uploaded.
  • The release notes now carry the APK's SHA-256 (next to the signing certificate) and link to THIRD_PARTY_NOTICES.md at the release tag. License texts already ship inside the APK under assets/licenses/.
  • The workflow still writes SHA256SUMS.txt for its own artifact check; the publish step now expects exactly one asset before un-drafting.
  • docs/RELEASE.md updated; the notes' data-export hint now points to 设置 → 关于与数据 → 数据管理.

Test plan

  • bash -n scripts/release_build.sh
  • Release rehearsal (throwaway key) on this PR, triggered because release.yml and release_build.sh changed

🤖 Generated with Claude Code

SHA256SUMS.txt and THIRD_PARTY_NOTICES.release.md are no longer uploaded.
The APK's SHA-256 and the signing certificate are printed in the release
notes, and the notes link to THIRD_PARTY_NOTICES.md at the tag; the
license texts already ship inside the APK under assets/licenses. The
workflow still writes SHA256SUMS.txt for its own artifact check, and the
publish step now expects exactly one asset.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Slacker-LLC
Slacker-LLC merged commit f347708 into main Oct 4, 2026
7 checks passed
@Slacker-LLC
Slacker-LLC deleted the chore/release-apk-only branch October 4, 2026 22:30
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