Repository navigation
Taskly 0.2.8 (unsigned evaluation)
Fixed
- Releases publish as normal releases so the moving
releases/latest/download/update-manifest.jsonfeed advances. GitHub only
resolves that endpoint for non-prerelease releases; while every build was
marked prerelease, v0.2.6 clients could never see v0.2.7. - The Linux AppImage in-place update no longer reports
path->string: contract violationafter the image has already been
replaced: the target stays a path end to end and the terminal state
publishesdownloadedPathbeforephase=downloaded. - The Windows portable-ZIP handoff resolves the packaged top-level directory
(taskly-windows-x64/) instead of assuming a flat archive, only writes
update-success.txtwhen the relaunch target exists, and clears a partial
payload before restoring the previous directory. - Update downloads reject HTML gateway-error pages instead of streaming them
into the size/SHA-256 check, and manifest fetches (Racket and macOS) retry
transient 5xx responses. - Linux persists the detected install shape immediately before every check,
removing the first-launch race between the 3 s silent check and the
fire-and-forget setting write. - macOS: the update service uses the real
taskly.appbundle name, cancelling
a download returns to the offer, and the published update ZIP now passes
codesign --verify --deep --strict(rivet builds it withditto, keeping
framework symlinks).
Linux AppImage upgrade note
Builds older than 0.2.8 (0.2.6/0.2.7) still carry the previous updater. Their
first update to 0.2.8 can report path->string: contract violation after
the new image has already been written: the old backend finished the rename,
then failed while recording the result. Quit and reopen Taskly once — the
0.2.8 image is in place, and every later update uses the corrected flow.
Changed
- The macOS release job verifies the update ZIP's code signature before
publishing. The release preflight now also checks the CHANGELOG section,
the manifest build number and the client-sync rivet pin. - README, the site and both user guides now list the real Linux asset names,
the actual check-update menu locations,/Applications/taskly.app, the
deb/rpm no-download path and Gatekeeper guidance consistent with the user
guide.