• v0.2.3 c251e4ded4

    mikebrandon released this 2026-09-18 23:16:34 +00:00 | 0 commits to main since this release

    Six defects in the update path, every one found by installing a release and using it, none by
    the 1,077 tests that pass.

    What was wrong

    The update button could not appear. The check feeding the only update control ran once on
    mount and never again, and the uploader stages seconds after that. The only way to see the
    button was to already have a staged update from an earlier session.

    Applying required capture to be running. The supervisor applies updates and existed only while
    capture ran, so installing a fix meant starting to record yourself.

    The button said "Download". By the time it appears the installer is already fetched and
    verified, so the press applies it — and it claimed not to stop capture and never said it was
    irreversible.

    A successful update jammed the next one. Nothing removed the staged artifact and the reader
    refuses to choose between two, so the second update any install was ever offered turned the
    surface off permanently. Every install reaches that state, and a successful first update is what
    causes it.

    An install on the newest build was told it had nowhere to look. Current existed in the code
    and was never constructed: an artifact is only staged when it is newer, so being up to date and
    never having looked were the same empty directory. The uploader now records what the feed named.

    A successful update reported itself as a failed check. The artifact an update was applied from
    stays behind and names the running version, which reads as "0.2.3 is not newer than the running
    0.2.3" — rendered everywhere as a failure, permanently, for everything having worked.

    Also

    Insights no longer promises that a day's capture "appears tomorrow": digests are written by the
    retention sweep, and a gate in reader mode asks for no sweeps, so nothing is summarised while
    capture is off.

    Signed, and proven before publishing:

    bundle: signed, and accepted by the key this build trusts
      trusted comment: timestamp:1789773345	file:here capture_0.2.3_x64-setup.exe
    

    SHA-256 b7b411e5c4f1020cf9364c02bc50aeed0e348a268b20cf6e0bf345d31d855c5a


    Where this came from. This repository is a distribution point, not the source. These bytes were
    built from HERE/Capture at 3007721.

    Downloads