Skip to content

Fix APK versionCode allocation after GitHub run ID overflow - #43

Merged
Noirero merged 3 commits into
betafrom
fix/distribution-version-code-allocation
Nov 15, 2026
Merged

Noirero merged 3 commits into
betafrom
fix/distribution-version-code-allocation

Conversation

@Noirero

@Noirero Noirero commented Nov 14, 2026

Copy link
Copy Markdown
Owner

Root cause

Run 43651042254 failed before Gradle: the old run-ID offset produced 2651042254, above 2100000000.

Change

Require an explicit decimal version_code for Beta and Stable manual builds. Tag builds read the repository variable LALAPO_RELEASE_VERSION_CODE. All three fail closed outside (2031852413, 2100000000]. Floor is the highest versionCode observed in successful archived workflow logs (Stable run 43031852413; Beta run 43027663597 used 2027663597). No signing, package or upload changes.

Distribution procedure

Before distributing, verify the highest versionCode actually shipped for the same applicationId and allocate a fresh higher value; the floor is not a registry and does not prevent reuse. For tagged release, set LALAPO_RELEASE_VERSION_CODE before the tag is pushed and allocate a new value for each release. Stable and tag workflows take effect only on refs containing this fix. Do not test via a publication tag.

Validation

Local Bash boundary tests pass (including failed run value, malformed input, lower and upper bounds). After review/merge to beta, dispatch a new Beta APK build on the exact merge SHA and verify APK metadata, signer, artifact upload and update-in-place from the previously installed Beta. No merge or release requested in this PR.

@Noirero
Noirero marked this pull request as ready for review November 15, 2026 01:32
@Noirero
Noirero merged commit 9f63635 into beta Nov 15, 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.

1 participant