Repository navigation
Release 1.24.0: reliable tracking and focused meal actions - #31
Merged
Merged
Conversation
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.
Release 1.24.0 keeps photo, manual entry and favorites immediately available, with the other meal tools under Additional actions. It fixes revoked-session access, analysis identifier validation, account isolation and durable photo review in offline queues, new-user water tracking, concurrent retries, meal dates and scaled nutrition totals.
Also adds modal keyboard support and pinch zoom, clarifies AI quality indicators, persists all normalized meal ingredients, and avoids full-state replacement for audit-only writes.
Validation: 164 unit tests, TypeScript, production build, two rendered HTML tests and the expanded file-store multi-user integration passed locally. Lint has no errors and 24 existing warnings. PostgreSQL ingredient persistence and container startup are covered by CI. Release version markers are synchronized.