Skip to content

Release 0.3.0 - #11

Merged
geeooff merged 2 commits into
mainfrom
release/0.3.0
Sep 23, 2026
Merged

geeooff merged 2 commits into
mainfrom
release/0.3.0

Conversation

@geeooff

@geeooff geeooff commented Sep 23, 2026

Copy link
Copy Markdown
Owner

The release commit for 0.3.0, and a fix to the installer found while preparing it.

What 0.3.0 carries — its CHANGELOG.md section

The configuration applies as you save it, a broken one says so, the games you marked yourself in the Game Bar are followed too, and the watcher costs a twelfth of what it did at rest.

  • Added: the configuration reloads within a second of a save, a game in progress undisturbed (Lot 9); a broken configuration shows as a red icon with a notification, and its end is said too; games marked by hand with Remember this is a game are detected from their launch or from a tick mid-game; at start, the log names the marked games Microsoft's own list now knows (Lot 15).
  • Changed: 0.026 % of a core at rest against 0.324 % for 0.2.0, measured; the watcher starts whatever the file says instead of exiting 3 or 4 at logon — the contract change that makes this a minor release in 0.x.
  • Fixed: a misspelt log_level used to leave a log with nothing but errors in it.

The two commits

  • Release 0.3.0 — version = "0.3.0", the [Unreleased] section turned into ## [0.3.0] - 2026-09-23 with a summary line, a stray blank line and an imprecise sentence fixed, [Unreleased] empty again, the compare links moved on.
  • Build the installer's cabinet in one piece, and refuse one that is not — the local build.ps1 release said release OK with an 88 KB installer: makecab's default disk is a 1.44 MB floppy, the executables had grown past it once compressed (1,476,966 bytes), and with a fixed cabinet name the second cabinet of the spanned set overwrote the first. The File table still listed four files, which is all the 102 evaluators check. Published, the installer would have failed on every machine — first on the update meant to close Lot 13. scripts/msi.ps1 now sets MaxDiskSize=0 and refuses a cabinet that expand -D does not show holding every file, or a build that left more than one. Recorded in docs/design/08-distribution.md.

Verified locally

build.ps1 release at 9acf017: checklist green, binaries stamped 0.3.0 (9acf0173), the changelog section found, 102 evaluators clean, installer 1.5 MB. An administrative extraction of the installer (msiexec /a, nothing installed) produced the four files at their exact sizes, and the extracted executable answers 0.3.0 (9acf0173).

After the merge

Tag v0.3.0 on the merge commit — on approval — and the workflow publishes. Then Lot 13 closes on the first update from a genuine 0.2.0 through the menu, on both machines.

🤖 Generated with Claude Code

geeooff and others added 2 commits September 23, 2026 16:03
The configuration reloads as it is saved and a broken one shows in the
icon with a notification (Lot 9), the games marked by hand in the Game
Bar are detected and the idle look costs a twelfth of what it did
(Lot 15). Minor, as a 0.x release with a contract change said in the
notes: the watcher no longer exits with 3 or 4 on a bad file at logon.
The changelog's section is dated, with a line saying what the release
is, and the Unreleased section is empty again.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 0.3.0 package came out at 88 KB: makecab's default disk is a 1.44 MB
floppy, the executables had grown past it once compressed (1,476,966
bytes), and with a fixed cabinet name the second cabinet of the spanned
set overwrote the first. The File table still listed four files, which is
all the 102 evaluators check, so the local release said OK. msi.ps1 now
sets MaxDiskSize=0, and refuses a cabinet that expand -D does not show
holding every file, or a build that left more than one. Recorded in the
distribution page: an installer that would have failed on every machine,
first on the update meant to close Lot 13.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@geeooff
geeooff merged commit 1f5c39e into main Sep 23, 2026
1 check passed
@geeooff
geeooff deleted the release/0.3.0 branch September 23, 2026 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant