Release 9.3.0: water and caffeine import, honest Effort, and an Oura resting-HR fix - #1000
Merged
Conversation
Notes covering everything merged since v9.2.1 (43 PRs), the in-app What's
New entry generated for both platforms, and the version bumps.
- docs/releases/v9.3.0.md — release notes plus the whatsnew front-matter,
with title translations for all five locales so the i18n gate has no
English fallback to warn about.
- AppChangelog.{kt,swift} + six strings.xml — generated by
Tools/appchangelog-gen.py, not hand-written, so the two platforms carry
byte-identical items.
- CHANGELOG.md — a 9.3.0 section in the existing house format.
- MARKETING_VERSION 9.2.2 -> 9.3.0, versionName 9.2.2 -> 9.3.0,
versionCode 305 -> 306.
The notes lead with a 'Scores that change' section because three merges
move numbers users have already seen — gap-weighted strain (#963), the
workout resting-HR fix (#983), and the sleep transition rule (#348) — and
the Oura fix (#375) corrects the importer, not rows already written, so it
needs a re-import to take effect.
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
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 notes for 9.3.0, covering everything merged since
v9.2.1(43 PRs), plus the in-app What's New entry and the version bumps.What's here
docs/releases/v9.3.0.md— the release notes, with thewhatsnewfront-matter the generator reads. Title translations are supplied for all five locales, so the generator has no English fallback to warn about.AppChangelog.kt/AppChangelog.swift+ sixstrings.xml— generated byTools/appchangelog-gen.py, not hand-written, so both platforms carry byte-identical items and Android gets a localised title rather than a raw literal.CHANGELOG.md— a 9.3.0 section in the existing house format.MARKETING_VERSION9.2.2 → 9.3.0,versionName9.2.2 → 9.3.0,versionCode305 → 306.Why the notes lead with "Scores that change"
Three merges move numbers users have already seen, and one needs an action from them. Burying that under "Fixed" would have people reading a changed Effort score as a new bug:
The iPhone permission prompt from #974 is also flagged, since an existing install will see a Health dialog it has never seen before and that is otherwise alarming.
Verification
Tools/i18n_audit.py --ci origin/main— exit 0. The new title key is present in all sixstrings.xmlwith real translations, French apostrophe correctly XML-escaped.Tools/doc_comment_lint.py— clean.src/main/javacompile. 2517 errors vs main's 2516; the single delta is one moreunresolved reference: RinAppChangelog.kt, which already has 270 of them becauseRisn't generated in an ad-hoc classpath. Exactly +1 for the +1 newuiString(R.string…)line, and Gradle generates the field from thestrings.xmlentry above.swiftc -parseclean onAppChangelog.swift.Tools/release-contributors.sh v9.2.1per CLAUDE.md, credited by@handle, third-party only.Note, not fixed here
CHANGELOG.mdhas no 9.2.0 or 9.2.1 section — its newest entry before this was 9.1.0, so this commit makes the file read 9.1.0 → 9.3.0. Both versions do havedocs/releases/notes and in-app entries, so only that one file has the gap. Backfilling it is a separate change and not mixed into a release commit.