Release v1.6.0 - #137
Merged
Merged
Conversation
Merge pull request #129 from Coding-Moves/develop
PUT /v1/me/notifications used cast(:times as time[]), which makes asyncpg infer
the param as time[] and then fail to encode the plain 'HH:MM' strings ('str'
object has no attribute 'hour'). Every save 500'd, so the reminder toggle
snapped back on and reminder-time changes never persisted.
Convert to datetime.time and bind with an ARRAY(Time) type. Extracted a
save_notification_prefs helper and added a regression test covering off/on and
new times.
The toggle already reverted its visual state on failure but did so silently. Surface an alert so a genuine offline failure isn't mistaken for the toggle being broken.
The saved list rendered inline on Profile, pushing Sign out and the version footer down as saves piled up. Move it to its own Profile-stack screen reached from a 'Saved concepts (N)' row, with a search box and category filter chips; the FlatList windows the rows for large lists. Each row still opens the concept detail. Profile keeps only the count. Removed the now-dead inline list, styles, and the composite navigation Profile no longer needs.
…134) - Fall back to All when the selected category no longer exists among saved concepts, so the list can't get stuck empty behind an invisible filter. - Profile's Saved-row count uses bookmarks.length, matching the activity card and updating optimistically, so the two counts never disagree. - Category filter chips persist taps, so the first tap after typing selects a category instead of just dismissing the keyboard.
Fix reminder toggle + move Saved Concepts to its own screen (#131)
JS-only release (runtimeVersion stays 1.3.0, ships OTA). Carries the backend reminder-preferences fix (#131) to main so Railway redeploys the api service. What's New lists the new Saved-concepts screen (search + filter); the reminder toggle fix is a bug fix, omitted per the features-only policy (#97).
Bump to v1.6.0 + What's New card
Muawiya-contact
added a commit
that referenced
this pull request
Sep 7, 2026
Merge pull request #137 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
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 v1.6.0 — JS-only, ships over the air on the production channel (runtimeVersion stays 1.3.0; no new APK).
What's in it
time[]binding), plus a failure alert.On merge to main, release.yml will
apiservice from main → the reminder-toggle fix goes live in production (the backend half only takes effect once it reaches main)Not included (separate, ops-only)
The
pool-topupcrash still needs the DB migrations applied to prod (concept_backlog.claimed_at+ the like-count index) — a release doesn't fix that.