From b8c9a519c115757981b298f42d3b51f09d7d1455 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Andr=C3=A9=20Bombeck?= Date: Thu, 30 Jul 2026 11:58:20 +0200 Subject: [PATCH] =?UTF-8?q?chore(release):=20v1.34.2=20=E2=80=94=20count?= =?UTF-8?q?=20a=20re-sent=20workout=20once=20on=20every=20surface;=20re-an?= =?UTF-8?q?chor=20the=20service-worker=20version?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Carries the four fixes that landed after the v1.34.1 tag plus the two found while reviewing them. The workout collapse that shipped in that batch only worked on the workout list, because it keyed a session on a field three of the five callers never fetched. Those three kept averaging one session into a person's baseline more than once. The service-worker fallback version had drifted a release behind with nothing checking it; both halves now have a gate. --- CHANGELOG.md | 29 +++++++++++++++++++++++++++++ docs/api/openapi.yaml | 2 +- package.json | 2 +- public/sw.js | 2 +- 4 files changed, 32 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index bcb5e8857..e99571f23 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,35 @@ ## [Unreleased] +## [1.34.2] — 2026-07-30 + +Point release. One workout that arrived more than once, and several surfaces +that were reading the same record differently from one another. + +### Fixed + +- Badminton recorded through Google Health keeps its sport instead of arriving + as "Other". Reported by @tarantila. +- A workout the same source sent twice is now counted once everywhere. The + workout list already collapsed the repeat, and the Coach narration, the + per-sport comparison and the workout deep link did not, so one session could + be folded two or three times into the averages a person is measured against. + The three that missed it were fetching the workout without its duration, and + the identity check needed that field. +- Insights prose renders at full contrast, and the two assessment cards share + one internal rhythm again after one of them drifted away from it. +- The dashboard headline survives for anyone who has switched the score lead + off. +- The service worker's fallback cache version follows the release again. It had + slipped a version behind, which only shows up in a browser that cannot load + the version file, and that browser then kept serving the previous release's + cached pages. + +### Credit + +Reported by @tarantila, directly rather than on the tracker: the badminton +mapping, following on from the workout-type loss in v1.34.0. + ## [1.34.1] — 2026-07-29 Security and reliability point release. diff --git a/docs/api/openapi.yaml b/docs/api/openapi.yaml index d6817840d..5938e2f0b 100644 --- a/docs/api/openapi.yaml +++ b/docs/api/openapi.yaml @@ -1,7 +1,7 @@ openapi: 3.1.0 info: title: HealthLog API - version: 1.34.1 + version: 1.34.2 description: >- Self-hosted personal-health-tracking PWA — public API surface for the iOS native client and external ingest. diff --git a/package.json b/package.json index b35f9000a..7e94e47ee 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "healthlog", - "version": "1.34.1", + "version": "1.34.2", "description": "Self-hosted personal-health-tracking PWA with Withings integration, AI insights, and doctor-report PDF export.", "license": "PolyForm-Noncommercial-1.0.0", "homepage": "https://healthlog.dev", diff --git a/public/sw.js b/public/sw.js index 4095c17dd..c247424d4 100644 --- a/public/sw.js +++ b/public/sw.js @@ -36,7 +36,7 @@ try { // v1.4.38.4 → v1.4.42. Do not hand-edit; bump `package.json` and rebuild. const CACHE_VERSION = (typeof self !== "undefined" && self.__APP_VERSION__) || - /* @sw-version-fallback */ "v1.34.1"; + /* @sw-version-fallback */ "v1.34.2"; const STATIC_CACHE = `healthlog-static-${CACHE_VERSION}`; const PAGE_CACHE = `healthlog-pages-${CACHE_VERSION}`; // v1.18.6 — read-only data cache for a curated allowlist of safe GET `/api/*`