v0.49.2
Это описание выпуска как оно опубликовано, а не его пересказ. Описания выпусков публикуются на том языке, на котором были написаны.
The release that makes the updater actually work. Both fixes needed a real machine to find, and neither could have been caught by a test.
An app left open never learned about a release
The update check ran once, at launch, and never again. Which is a check this app never gets to make: Chimera is a working tool — it stays open, and the launch that would have found the release happened yesterday.
Measured, from the outside, with the sharpest possible evidence: 0.49.1 was published, the app offered nothing, and the installer was fetched from the website by hand.
It looks again every six hours now, for as long as the app runs.
Two things had made it worse, both shipped earlier the same day. The tray's Check for updates — introduced in 0.49.0 as "the way to ask" — sits behind the hidden-icons chevron on a default Windows install, which nobody measured before recommending it. And holding a release back from "latest" until its installers finish (see below) widened the period in which a launch finds nothing, from the instant of publication to the whole build.
Checking every six hours would mean asking every six hours, which is the nagging the automatic path has always avoided. So declining an update remembers that version for the life of the process; a newer one asks again, which falls out of comparing rather than needing a rule of its own. A check you asked for by clicking the menu item always asks — answering "you already declined that" to somebody who just requested it would be refusing what they asked for.
The installer fix starts working with this one
0.49.1 shipped a fix for an upgrade that left the previous version's files behind — _internal ended up holding two chimera_agent-*.dist-info directories, and the app reported the version it used to be, so it kept offering an update to itself.
That fix repairs the installer a release ships, not the one that installs it. 0.49.2 is the first release whose in-place update runs the repaired installer. If you updated to 0.49.1 from inside the app and the badge lied afterwards, this is the release that stops it.
Also in 0.49.1, if you skipped it
- Releases are held back from "latest" until their manifest is attached. The updater endpoint used to 404 for the whole twenty-five minute build, silently, because the check swallows errors so it never nags.
- The failure dialogs and the tray speak the reader's language; the technical diagnostics deliberately do not, because a translated system error is one nobody can search for.
- The first-run wizard's cost modes are no longer four English words on a translated screen.
Full notes: CHANGELOG.md