The first release is a beta: 0.1.0-beta.1, published as a pre-release #13
Loading…
Reference in a new issue
No description provided.
Delete branch "beta-release"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The first Android release becomes a beta,
0.1.0-beta.1.versionNameis0.1.0-beta.1.versionCodestays 1, because nothing has been released yet and the workflow only needs it to be above every earlier release's.scripts/sign-release.sh: both checked^v?[0-9]+\.[0-9]+\.[0-9]+$and refused a pre-release suffix. They now acceptMAJOR.MINOR.PATCHwith an optional-part(.part){0,3}suffix. It's one pattern, the same as unfret_backend'sunfret.android_release."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.jsongets"prerelease": true|false. unfret.net/android reads that field and labels the release "Beta" (backend PR in unfret_backend, branchandroid-beta)./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.isBeta./androidstep nowgit adds the newandroid-release.json, becausecommit -amisses it the first time. The changelog, README and PRIVACY are updated with the version.Checked locally:
make checkpasses.make release-apkbuildsdist/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