@aws-sdk/client-s3 3.1169 and lib-storage 3.1167, @napi-rs/canvas 1.1.1,
@simplewebauthn/server 14.1.0, @tanstack/react-query 5.107.1,
dotenv 18.0.10, jose 6.2.17, lucide-react 1.73, mmdb-lib 3.0.5,
nodemailer 10.5.0 and pg-boss 12.38.2.
The pins that hold these move after reading the installed sources:
- pg-boss 12.38.2 keeps the failed-row ledger the 72-hour reader relies
on: deletion still runs on completed_on + deletion_seconds against
job_now(), with the 14-day retention, 7-day deletion, 15-minute expiry
and two retries unchanged. The release only moves keep_until along
with start_after on retry and resume.
- @simplewebauthn/server 14.1.0 adds passkeyProviderMetadata to the
registration result. It is filled only by an initialised FIDO metadata
service, which downloads from the FIDO Alliance; HealthLog initialises
none, so the contract now pins the field as absent. The stored key
bytes are unchanged. The new origin and RP ID checks reject a trailing
slash or non-ASCII form, and both values already come from URL.origin
and URL.hostname.
- dotenv 18.0.10 moves its CLI to a separate entry; the library API is
unchanged. The Prisma CLI stage installs the same version.
postgres:18.6-trixie now resolves to e3d24f6, a multi-arch index with
linux/amd64 and linux/arm64 on the current Debian trixie-slim base. The
PostgreSQL package is unchanged (18.6-1.pgdg13+2).
node:22-trixie-slim now resolves to 68c76cf, a multi-arch index with
linux/amd64 and linux/arm64 that carries Node 22.23.5, a security
release with HTTP, HTTP/2 and TLS fixes. All four Node stages and the
release guard move to the new digest together.
A night on which every account was skipped, for instance because every
provider was paused for background work, wrote all_failed false. The
repeated-failure alert read that as a successful run: it ended the
streak and announced a recovery while the provider was still down, and
nights then alternated between failed and paused so the streak never
reached the alert again.
The run now also records run_attempted. A completed run with
run_attempted 0 is neither a failure nor a recovery: the alert and
readConsecutiveRunFailures step over it.
Refs #1384
The footer reserve under a day-linked chart's loading shell still held the
caption line that was dropped from those charts, so every such shell stood
20 px taller than its chart (40 px on a phone). The dashboard's mood chart
loaded behind the generic shell, which is about 30 px shorter than the
mood card. When the shared chart chunk arrived late the dashboard's chart
row changed height under a reader already scrolled past it; the tablet
shell journey measured <main> right after such a swap and found it no
longer at its end.
The reserve now holds only the day rug, and the mood chart gets a shell
built from the same card primitives and boxes. The tablet journey also waits
for every chart cell to reveal and every loading shell to go before it
scrolls to the end, instead of trusting two equal heights 250 ms apart.
Raising the record-session hold clears the query cache, which remounts the
account query, so the switching tab has a GET /api/auth/me in flight beside
its own POST /api/account/switch. When the server answered that read from
the record being left and the answer was applied after the commit, fetchMe
rewrote the scope mirror back to the old record. A peer tab that had already
settled read that write as a foreign switch and published a hold expecting
the old record, which no /me would ever confirm, so every tab sat behind the
hydration gate until the stored transition aged out.
The transition store now counts the changes a tab applies, and fetchMe
repeats a read whose request straddled one instead of applying it.
The nightly briefing pass settled an account as failed whenever its
generation failed, including when every provider of its chain was
benched for background work and no request was sent, and when the
provider refused the account's own credential. A key revoked at its
issuer stays saved and is refused every night, so a single-account
instance read as all-failed night after night and the repeated-failure
alert reported a broken job.
- A chain that sent nothing settles as skipped (provider_benched), with
no 45-minute retry.
- A refused credential of the account's own settles as auth_failed,
which the run reports as partial but does not fail over; a refusal of
the operator's shared key still fails the run.
- The generator's failed outcome names the provider that failed first,
whether its credential was refused and whether anything was sent.
- The run's facts carry failure_cause and failure_provider.
The admin Background jobs card listed only pg-boss failures, while the
alert also counts runs that completed with every account failed, so an
operator sent to the card read that nothing had failed. The card now
lists those runs, and the card and the alert describe them in words
with the cause and provider instead of quoting the run's JSON.
The warm tally counted a status card that fell back to its deterministic
text as a warmed assessment; it now counts model-written notes only.
Refs #1384
The note field imported its length limit from the validation module,
which pulled zod and the medication request schemas into the client and
put the medications list and detail pages over their bundle budget. The
limit lives in a zod-free module now, and the validation re-exports it.
Directions such as "30 to 60 minutes before food" had nowhere to go: a
medication carried no free text of its own, only the notes on a dose
change or a course. The medication now has one note, edited on the last
step of the wizard and shown under the name on the detail page, above
the dose actions on both card variants, under the picked medication in
the log-dose sheet, and per row in the take-all-due list. One
MedicationNote component renders it everywhere, in foreground text.
The note is sealed at rest in Medication.noteEncrypted (migration
0498_medication_note, lock-bounded), with no plaintext column. Create
and update take an optional `note`: trimmed, at most 500 characters, an
empty string or null clears it, absent keeps it. The wizard sends it on
an edit only when it changed, so an unrelated save never clears it. The
list and detail reads strip the ciphertext and answer `note`.
Both ends of the data path carry it: the backup (decrypted in a portable
file, ciphertext in a disaster-recovery file), the restore, the data
export, the key-rotation registry and script, and the MCP medication
schedule, resources and fetch, fenced as user text. The doctor report
and the FHIR export leave it out: it is the person's own reminder, and
the report has no selection for personal prose.
The size baselines rise by the one-line wiring of the field in the
medication page, detail tabs, cards, log-dose sheet, wizard step and
list read; the wizard payload grows by the field's own encode and
hydrate.
Enabling Browser Push showed only "Activation failed" whenever
pushManager.subscribe() rejected. Brave keeps push messaging off by
default and rejects with "AbortError: Registration failed - push
service error", which left people with nothing to act on.
The browser's own refusal is now classified apart from the server
answers around it. An AbortError from subscribe reads as the push
service refusing and links the Browser Push docs; in Brave the message
names the setting under brave://settings/privacy. A blocked permission
stays blocked, and a dismissed prompt or a rejected key keeps the
generic message. The subscribe flow moves out of the card component so
it stays under the function size baseline.
Refs Discussion #1378
The record switcher opened as a side sub-menu next to the account menu.
On a phone the account menu sits against the right edge and takes most
of the width, so the 240 px sub-menu had room on neither side and ran
off the screen with the names cut off. Below the sm breakpoint the
trigger now unfolds the records in place inside the account menu;
wider screens keep the sub-menu. The trigger, list and entry slots are
unchanged, so the journeys read the same at either width.
Refs #1372
A script or a home-automation rule holding a measurement token can now
post a value to POST /api/custom-metrics/{id}/entries for a custom metric
its owner already created. The route names MEASUREMENTS_WRITE_SCOPE on
the POST only; the value list, the metric list and every create, edit,
delete and restore leg still name no scope and refuse the token 403.
The token stays on its owner's record: requireAuth refuses any account
selector, and an id that is unknown, deleted or another account's answers
the same 404. The entry has no source column, so the audit row names the
token that wrote it.
The bearer-scope guard now freezes the scope's reach at three files, with
the custom-metric file naming it once and only on the POST. Integration
cases cover the admitted write, idempotent retry, the foreign and deleted
ids, five other narrow scopes, every other custom-metric leg, and a shared
record. The OpenAPI descriptions and the token card text in every locale
say what the token can do and where a metric's id is found.
Refs #1377
The averages on a dashboard tile open their colour hint on a tap now,
which made them touch targets of 16 px height. On a touch screen the
trigger is 44 px tall, and a negative margin keeps the tile's line
where it was.
Opening a sheet pushed a history entry, and closing it took that entry
off again with a history back. The browser answers that back later, so
when the close started a navigation it landed after the router's push
and undid it: the medication wizard stayed on the list instead of
opening the new medication, a section picked from the settings list on
a phone stayed on the account page, and a link followed from a sheet
could put the page under it back.
The sheet history goes, with its wiring in ResponsiveSheet, the
document sheet's opt-out, the account form's deference to it, Back
answering the discard question, and their tests. Back behaves as
before: it leaves the page and the sheet goes with it, and the account
form's own Back guard answers every Back again. A tap outside, Escape,
the X and a swipe still ask before dropping typed input. The two size
baselines return to their earlier numbers.
A badge call from the service worker stalled Chromium's worker thread
while it activated, awaited or not: the worker reached "activated" but
never claimed its pages, so no page was ever controlled and every
offline path was gone. The worker no longer touches the badge. The
installed app clears a leftover count from the page once the worker is
registered; a browser tab leaves it alone.
The filter-sync test no longer reads `history.length`, which the
browser caps; the recorded push without a replace already proves the
new entry.
The two ketone cases repeated the glucose cases with one type changed; they are now one parametrized case each, which keeps the mocked client casts at their count.
The Fitbit guide still called the integration experimental and spoke of
the 30 October 2026 turndown as ahead. Three new files carried em
dashes in a doc comment and two test titles.
- The About button opens the release notes and now says so in all ten
languages; six of them still showed the English word "Changelog".
- The discard question now also covers edit sheets, where "Discard this
entry?" read like deleting the target or episode being edited. It
asks about the changes in every language; Russian also loses the
ambiguous "Отменить" on both the title and the button.
- The 7-day trend figure on a dashboard tile had an English screen
reader label in every language.
- Outlier terms in the new checkup and ketone strings follow each
catalog (ru "Кетоны в крови", "Коуч"; es "Desactivado"; nl
"rusthartslag"), the French steps question reads naturally, and the
shared Polish and Russian Coach question no longer assumes a
masculine speaker.
The case with a year of earlier takes proved the ledger stays the same,
which the old read of every intake satisfied as well, so a revert of
the bounded read passed every test. It now also counts the rows the
route read and expects only the window's.
- README: the integrations line now names Strava, Garmin and the Health
Connect import, the reminder channels include email and the webhook,
and the last two feature labels say what they cover.
- UI guidelines: the password form was said to carry a hidden username
field it does not have; the line now states when one helps.
- CONTRIBUTING: strings go into every locale file, not only English and
German.
- The translation issue template called eight locales "AI-initial",
left Russian out of its list and its dropdown; it now says they
started as machine-translated drafts reviewed by the community.
- The pull request template asked for two locales where the checks
require all ten, and pointed at an ignored docs folder.
- Code comments named the maintainer notes file, a release by its
working name and an internal host; old changelog entries explained
the notes files by their tool-specific names. A fixture token and
the deploy webhook test's application id (a real one) are replaced.