Repository navigation
Release Helix 1.2.5 and harden APK CI - #10
Merged
Merged
Conversation
Separate app and Firebase Functions TypeScript validation and update Actions to Node 24-
compatible versions.
Confidence: high
Scope-risk: narrow
FatBoy721
marked this pull request as ready for review
July 23, 2026 19:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
latesttag/changelog handlingWhy
The v1.2.5 APK was published from
play-store-prep, whilemainremained behind and the existing Actions workflow could generate a Play-channel APK for GitHub. The rollinglatesttag was also stale, which caused accumulated release notes.Validation
npx tsc --noEmitnpx eslint . --quietnpm run test:regressions— 47 checks passednpm run build --prefix functions./gradlew testReleaseUnitTest --no-daemongit diff --checkThis PR is intentionally draft until GitHub Actions completes successfully and the merge/release sequence is confirmed.