Skip to content

v0.2.0

@ianiemeka14 ianiemeka14 tagged this 16 Oct 08:52
0.2.0 rather than 0.1.5 because the updater compares the shipped number,
and 0.1.5 is lower than the 0.1.13 that briefly existed; installs on it
would never have updated again. Jumping the minor clears it, and from here
the internal number and the published label are the same thing.

The split did its job -- the public history reads as a normal sequence and
that is permanent -- but it had to be paid for every release: a rename
between build and upload that release-manifest.sh refuses to support, a
hand-edited manifest url, and a same-named installer from weeks earlier
sitting in the output folder every single time, with a sha256 check as the
only thing between it and a stale binary going out correctly signed.

None of that applies now. The build emits the name that gets published and
the manifest is right as generated.

Ships the retime fix and the pan-axis fix.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assets 2
Loading