The first release is a beta: 0.1.0-beta.1, published as a pre-release #13

Merged
kroshtan merged 1 commit from beta-release into main 2026-11-18 20:44:45 +00:00
Owner

The first Android release becomes a beta, 0.1.0-beta.1.

  • versionName is 0.1.0-beta.1. versionCode stays 1, because nothing has been released yet and the workflow only needs it to be above every earlier release's.
  • Release APK workflow and scripts/sign-release.sh: both checked ^v?[0-9]+\.[0-9]+\.[0-9]+$ and refused a pre-release suffix. They now accept MAJOR.MINOR.PATCH with an optional -part(.part){0,3} suffix. It's one pattern, the same as unfret_backend's unfret.android_release.
  • A beta's Forgejo release is created with "prerelease": true, and its body starts with one line saying it is a beta. If a release already exists with a flag that disagrees, the run stops.
  • release.json gets "prerelease": true|false. unfret.net/android reads that field and labels the release "Beta" (backend PR in unfret_backend, branch android-beta).
  • The versionCode check read /releases/latest, which leaves out pre-releases. With betas that check would never have run. It now goes through every published release, betas included, and compares against the highest versionCode.
  • The About screen adds one sentence under the version for a beta: "This is a beta, an early version: things may still change. Tell us what doesn't work at hello@unfret.net." A unit test covers isBeta.
  • docs/RELEASING.md has a new section, "Versions and betas". The /android step now git adds the new android-release.json, because commit -a misses it the first time. The changelog, README and PRIVACY are updated with the version.

Checked locally: make check passes. make release-apk builds dist/unfret-0.1.0-beta.1-unsigned.apk, and its aapt2 badging matches the line the signing script expects. The workflow's release check, run against the forge, finds no problems for main.

🤖 Generated with Claude Code

https://claude.ai/code/session_014HgVKRoNZC5gcKdzyYgCWJ

The first Android release becomes a beta, `0.1.0-beta.1`. - `versionName` is `0.1.0-beta.1`. `versionCode` stays 1, because nothing has been released yet and the workflow only needs it to be above every earlier release's. - **Release APK workflow and `scripts/sign-release.sh`**: both checked `^v?[0-9]+\.[0-9]+\.[0-9]+$` and refused a pre-release suffix. They now accept `MAJOR.MINOR.PATCH` with an optional `-part(.part){0,3}` suffix. It's one pattern, the same as unfret_backend's `unfret.android_release`. - A beta's Forgejo release is created with `"prerelease": true`, and its body starts with one line saying it is a beta. If a release already exists with a flag that disagrees, the run stops. - `release.json` gets `"prerelease": true|false`. unfret.net/android reads that field and labels the release "Beta" (backend PR in unfret_backend, branch `android-beta`). - **The versionCode check** read `/releases/latest`, which leaves out pre-releases. With betas that check would never have run. It now goes through every published release, betas included, and compares against the highest versionCode. - The About screen adds one sentence under the version for a beta: "This is a beta, an early version: things may still change. Tell us what doesn't work at hello@unfret.net." A unit test covers `isBeta`. - docs/RELEASING.md has a new section, "Versions and betas". The `/android` step now `git add`s the new `android-release.json`, because `commit -a` misses it the first time. The changelog, README and PRIVACY are updated with the version. Checked locally: `make check` passes. `make release-apk` builds `dist/unfret-0.1.0-beta.1-unsigned.apk`, and its aapt2 badging matches the line the signing script expects. The workflow's release check, run against the forge, finds no problems for main. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_014HgVKRoNZC5gcKdzyYgCWJ
The first release is a beta: 0.1.0-beta.1, a Forgejo pre-release with "prerelease" in release.json
All checks were successful
CI / extractor (pull_request) Successful in 10s
CI / android (pull_request) Successful in 4m15s
4fff7beceb
versionName is 0.1.0-beta.1 (versionCode stays 1: nothing is released yet). The Release APK workflow and
scripts/sign-release.sh accept a version with a pre-release suffix (one pattern, the same as unfret_backend's),
create the Forgejo release as a pre-release, and write "prerelease": true|false in release.json, which
unfret.net/android reads to label a beta. The versionCode check now looks at every published release, betas
included: /releases/latest leaves pre-releases out. The About screen says, under the version, that this is a
beta. docs/RELEASING.md: "Versions and betas"; the /android step adds the new facts file explicitly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014HgVKRoNZC5gcKdzyYgCWJ
kroshtan deleted branch beta-release 2026-11-18 20:44:45 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kroshtan/unfret_android!13
No description provided.