From f314fe1a3a4f97dfcf884e72ebdf08ab7fcc0242 Mon Sep 17 00:00:00 2001 From: Taylor Addison Date: Mon, 19 Oct 2026 18:53:48 -0400 Subject: [PATCH] CHANGELOG: #101 is unreleased, not part of 0.9.1 #101 merged into develop after the 0.9.1 release, and the merge placed its bullets under the renamed [0.9.1] heading. v0.9.1 does not contain it. Co-Authored-By: Claude Opus 5.5 --- CHANGELOG.md | 49 ++++++++++++++++++++++++++----------------------- 1 file changed, 26 insertions(+), 23 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 38bfa0e..97375d7 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -16,31 +16,8 @@ a CI job fails when they disagree. ## [Unreleased] -## [0.9.1] — 2026-10-18 - -A phone on the shelf is woken before it is driven, and one with a PIN says so -instead of failing as if the app were broken. The lab gains a regression -nightly on the bug garden. - -### Added - -- **`nightly-bug-garden-regressions`, a regression nightly on the bug - garden.** Bug garden's smoke flow plus every bug-garden finding marked real - and then fixed, replayed on the shelf's Android phone at 02:45 - (`seed-schedules`, off on a fresh collector; the lab has it on). The - garden's defects are planted, so a finding marked fixed comes back and - reopens: proved once on ultra's emulator, where finding #18's crash recurred - and reopened it. ([#100](https://github.com/addisdev/fleet-runner/pull/100)) - ### Fixed -- **A sleeping phone failed its UI tests as if the app were broken.** Maestro - does not wake a device, so `nightly-fleet-ui-smoke` ran against the Galaxy - S8+'s lock screen and failed `"Fleet Runner" is visible` every night. - `ui-test` and `locale-shots` now wake an Android device and dismiss a lock - screen with no PIN first; a PIN, pattern or password makes that device's row - `skipped` with the reason, since nothing here can get past it. - ([#100](https://github.com/addisdev/fleet-runner/pull/100)) - **A model unloaded mid-night is loaded again.** On ultra the model shelf unloads an on-demand model it sees idle under memory pressure, and between two missions Holo4 is idle: on the first three 0.9.0 nights it was dropped @@ -80,6 +57,32 @@ nightly on the bug garden. pull request (#98) failed its own `develop` → `main` check and had to be labelled `no-changelog` by hand. ([#101](https://github.com/addisdev/fleet-runner/pull/101)) +## [0.9.1] — 2026-10-18 + +A phone on the shelf is woken before it is driven, and one with a PIN says so +instead of failing as if the app were broken. The lab gains a regression +nightly on the bug garden. + +### Added + +- **`nightly-bug-garden-regressions`, a regression nightly on the bug + garden.** Bug garden's smoke flow plus every bug-garden finding marked real + and then fixed, replayed on the shelf's Android phone at 02:45 + (`seed-schedules`, off on a fresh collector; the lab has it on). The + garden's defects are planted, so a finding marked fixed comes back and + reopens: proved once on ultra's emulator, where finding #18's crash recurred + and reopened it. ([#100](https://github.com/addisdev/fleet-runner/pull/100)) + +### Fixed + +- **A sleeping phone failed its UI tests as if the app were broken.** Maestro + does not wake a device, so `nightly-fleet-ui-smoke` ran against the Galaxy + S8+'s lock screen and failed `"Fleet Runner" is visible` every night. + `ui-test` and `locale-shots` now wake an Android device and dismiss a lock + screen with no PIN first; a PIN, pattern or password makes that device's row + `skipped` with the reason, since nothing here can get past it. + ([#100](https://github.com/addisdev/fleet-runner/pull/100)) + ## [0.9.0] — 2026-10-15 Green that means something. A job that ran nothing is `skipped`, not `done`,