Release 1.9.1: learning highlights and one-time What’s New card - #205
Merged
Merged
Conversation
Merge pull request #200 from Coding-Moves/develop
release: prepare 1.9.1 and its What’s New card
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
1 participant
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.
One Concept 1.9.1
Release
develop→mainwith the requested version bump and a matching one-time What's New card. This carries forward the already-merged learning improvements; it does not introduce another implementation or claim a mobile update has already shipped.What users will see
The 1.9.1 card is eligible even if the user previously dismissed 1.8.0 or 1.9.0; after dismissal it stays hidden for 1.9.1. App version 1.9.1, native runtime unchanged at 1.3.0. No new migrations or dependencies.
Deployment
Merging main lets Railway deploy the new revision. It does not publish mobile OTA automatically. Verify the deployed API and workers and production health, then manually run Release on main with the full verified commit SHA. Keep generation paused until compatible workers are confirmed. Prior migrations 0011–0015 are already verified and recorded. The existing local backup was not uploaded or restored.
Validation
Node 24 typecheck and all 39 tests passed. Clean Android/iOS/web exports passed. Mocked browser checks in both themes confirmed four 1.9.1 highlights for 1.8.0/1.9.0 upgrades and dismissal persisting after reload. Screenshots inspected; preparation #204 records the results. Physical Android OTA installation remains unverified until publication. Preserve commit history with a merge commit; do not squash.
Permanent rule for every future release
Every release PR must include both the release version bump and its matching, nonempty one-time What's New card in the final diff against main. Automatically verify both and document the version, benefits and card validation in the PR description; no owner reminder is needed. This rule is saved in AGENTS.md and RELEASING.md, saved on develop through #206 after this release PR merged. The permanent rule files are not part of the already-merged #205 diff.
For this release: 1.9.1 in
mobile/app.config.jsand 1.9.1 inmobile/src/data/whatsNew.tsare both present. The browser preview confirmed four highlights and per-version dismissal in both themes.