test #3

Merged
brian merged 2 commits from test into main 2026-07-21 18:46:03 +00:00
Owner
No description provided.
Fix for deploy.yml
Some checks failed
Build and Deploy / test (push) Successful in 25s
Build and Deploy / build (push) Successful in 10s
Build and Deploy / deploy-main (push) Has been skipped
Build and Deploy / deploy (push) Failing after 8s
b7312b9976
Fix for deploy.yml
All checks were successful
Build and Deploy / test (push) Successful in 25s
Build and Deploy / build (push) Successful in 7s
Build and Deploy / deploy-main (push) Has been skipped
Build and Deploy / deploy (push) Successful in 13s
949676ca80
Drive/Nextcloud/on-close backups now export memories the user owns
(metadata, transcripts, tags, shares) with media and photo blobs pushed
to the same hash-named incremental blob store as attachments. Restore
recreates them, re-fetching blobs; backups without a memories section
(schema 1, older clients) leave memories untouched. Schema bumped to
journal-backup/2.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Day files, memory media, and memory pictures now upload via XHR with a
live progress bar, then verify the server-stored copy (byte count, plus
SHA-256 when the file is small enough to hash locally). Corrupted or
failed uploads surface an error; queued memory uploads stay pending and
retry on the next sync, and a corrupted day-file attachment is deleted
server-side before asking the user to retry.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
chore: ignore .aider files
All checks were successful
Build and Deploy / test (push) Successful in 24s
Build and Deploy / build (push) Successful in 8s
Build and Deploy / deploy-main (push) Has been skipped
Build and Deploy / deploy (push) Successful in 13s
54364aaf73
chore: ignore .aider files
All checks were successful
Build and Deploy / test (push) Successful in 24s
Build and Deploy / build (push) Successful in 6s
Build and Deploy / deploy-main (push) Has been skipped
Build and Deploy / deploy (push) Successful in 13s
3b32fa21ef
feat: configurable per-user timezone for journal dates
All checks were successful
Build and Deploy / test (push) Successful in 23s
Build and Deploy / build (push) Successful in 25s
Build and Deploy / deploy-main (push) Has been skipped
Build and Deploy / deploy (push) Successful in 15s
ed994524eb
Backend already stored every moment-in-time column as UTC TIMESTAMPTZ;
the real gap was that "what day is it" for journal pages/attachments was
decided entirely by the browser's local clock. Add a per-user `timezone`
preference (default America/Boise) surfaced via /api/settings, and route
all frontend "today"/date-display logic through it instead of raw
browser-local Date getters.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
brian merged commit 7b1f6f8dc7 into main 2026-07-21 18:46:03 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
brian/Journal!3
No description provided.