Skip to content

SyncPilot 0.8.3

Choose a tag to compare

@github-actions github-actions released this 14 Oct 23:32
· 81 commits to main since this release

The release-hygiene round: everything below tightens how SyncPilot ships
and reports itself — feedback surfaces and release gates, no change to the
app's own behaviour.

Added

  • GitHub issue templates (bug report + feature request) so feedback
    lands structured: the bug form asks for the distro/desktop-environment
    pair, the package shape and the rslsync binary provenance — the three
    facts every Linux-only report needs — and points update failures at the
    now-copyable dialog text. The manual (syncpilot.jrtx.site/guide.html)
    is offered as a contact link before a blank issue.
  • The release ships the signed feed under both names. Release assets
    carry update-stable.json — what shipped since 0.7.0 and what current
    hosts still fetch — plus its byte-identical twin update-manifest.json
    (the family-standard feed name; the signature covers the payload, not
    the filename, so both verify). Zero client change this round; the twin
    exists so the feed name can migrate client-side later without
    re-releasing.

Changed

  • The About card names the issue tracker. The About text now ends
    with github.com/turinglambdaai/syncpilot/issues (zh and en, plain
    text in the i18n single source), beside the existing repo link — a bug
    report starts one glance away from the About card that describes it.
  • Update failure text is selectable. The update dialogs' message
    label (errors and status alike) is a selectable GTK label, so the exact
    failure text — URLs, errno strings — can be copied out instead of
    retyped.
  • CI single-sources the rivet pin: both workflows declare a
    workflow-level RIVET_PIN env and every raco pkg install references
    it, so a rivet bump is one edit per file (the setup-embed-racket
    uses: pins stay literal — GitHub does not allow expressions there).
    setup-racket rides along at v1.15.

Fixed

  • The release preflight gates the generated client's version stamp.
    check-release-version.sh now reads kVersion from
    linux/GeneratedBackend.hpp and requires it to equal VERSION (the
    GeneratedBackend.swift gate autarx already had, ported) — 0.8.2 shipped
    while the hpp still stamped 0.8.0 and nothing checked it. The stamp was
    corrected after the fact, so this release is the first whose generated
    client matches its version on day one; four gates (VERSION ==
    rivet.rktd == updater identity == generated stamp, plus tag and
    CHANGELOG) now stand between main and a mislabeled release.