Skip to content

Commit e28a1eb

Browse files
docs: move the Current Version paragraph to 0.4.6 (#168)
Publishing 0.4.6 left the hand-written "Current Version" paragraph at 0.4.4. The Release Log and the Package Status Table were already correct, because #152 maintains those automatically; the narrative sentence is deliberately human and has to be moved by hand. Also corrects the contribution count. With #161 shipping in 0.4.6 there are four external good-first contributions rather than three, from three different people, and the paragraph now names the three that landed in the 0.4.x line: 0.4.3 (#104, PR #133), 0.4.4 (#138, PR #147) and 0.4.6 (#137, PR #161). Closes #167
1 parent 9f2e00d commit e28a1eb

1 file changed

Lines changed: 7 additions & 6 deletions

File tree

‎CURRENT_STATE.md‎

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,13 @@
88
99
## Current Version
1010

11-
`0.4.4`, firmware-update-failure scenario (published 2026-07-30). The v0.4.x
12-
interop and correctness milestone is complete; the line continues to take patch
13-
releases for scenario additions. `0.4.3` and `0.4.4` each carry a
14-
`good-first-issue` completed by an outside contributor: after
15-
`REPEATED_BOOT_NOTIFICATION` (Issue #105, PR #114) in `0.3.1`, that is three
16-
external good-first contributions in total.
11+
`0.4.6`, heartbeat-timeout scenario (published 2026-08-08). The v0.4.x interop and
12+
correctness milestone is complete; the line continues to take patch releases for
13+
scenario additions. Three of those patches each carry a `good-first-issue`
14+
completed by an outside contributor, `0.4.3` (Issue #104, PR #133), `0.4.4`
15+
(Issue #138, PR #147) and `0.4.6` (Issue #137, PR #161). With
16+
`REPEATED_BOOT_NOTIFICATION` (Issue #105, PR #114) in `0.3.1`, that is four
17+
external good-first contributions in total, from three different people.
1718

1819
## Release Log
1920

0 commit comments

Comments
 (0)