Release v1.4.1 (JS-only — About screen, heart Like icon, one-round-trip startup) - #118
Merged
Conversation
Release Develop > Main
The production-apk profile already sets environment/channel; passing --environment to eas build diverged from the working eas-build.yml. Also capture both output streams so a build failure is printed instead of hidden by --json.
release-apk.yml can't listen for the release event (GitHub suppresses events raised by GITHUB_TOKEN), which is why the APK didn't build automatically. Have release.yml dispatch it via 'gh workflow run' (workflow_dispatch is exempt from that rule), so a native release builds and publishes the stable APK link with no manual step. Grants actions:write for the dispatch.
Auto-build the production APK on release (zero manual steps)
GET /v1/me/state now also returns today's concept (via get_or_create_daily), so the app fetches everything in one request at startup. Null 'daily' means the catalog is exhausted. Same create-on-first-call behaviour as GET /v1/daily.
DailyPayload/DailyOutcome move to types/ (so ProgressState can reference them without an import cycle). dailyApi keeps only toConcept + clearDailyCache; the standalone /v1/daily fetch and its cache are gone now that the concept rides on the server state.
…ly (#102) Parse the folded 'daily' into ProgressState.serverDaily and expose it from ProgressContext; TodayScreen reads it instead of a second /v1/daily fetch. On an offline load-fallback the daily is flagged stale (the offline banner), while the cache-first preview stays not-stale (#92 preserved). One startup round trip.
Fold today's concept into /v1/me/state — one startup round trip (#102)
The Like button and like-count badge used the same flame icon as the streak, which was confusing. Give Like a heart (heart/heart-outline) in the rose 'like' colour; the streak keeps its orange flame.
A tappable 'About' row (info icon) under Personalize opens the new modal.
Features-only per #97: the About screen is the new feature; the 1.4.1 card leads with it. Entry is dormant until the release bumps expo.version to 1.4.1.
Use a heart for Like, distinct from the streak flame (#114)
Add an About screen (reachable from Profile)
chore: bump to v1.4.1 (JS-only)
Muawiya-contact
added a commit
that referenced
this pull request
Sep 5, 2026
Merge pull request #118 from Coding-Moves/develop
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.
Release v1.4.1 — promotes
developtomain. JS-only (noruntimeVersionchange) → ships over the air, no reinstall.New feature
Improvements & fixes
What happens on merge (the workflow test)
release.yml→ publishes production + preview OTA and cuts thev1.4.1tag + Release.release.ymldispatchesrelease-apk.yml→runtimeVersionis unchanged (1.3.0) → it skips the APK build and leaves the stableapk-latestlink as-is.Result on your phone
This is the end-to-end test of the JS-only release path + the APK native-gating.