Skip to content

Auto-update #200

Open
Open

Description

@omesser

Split from #18. Depends on: #132

Why

A companion should update itself so the user does not have to track releases.

Scope

  • Replace the placeholder minisign pubkey in src-tauri/tauri.conf.json with the key that signs GitHub Release artifacts from Build and distribute macOS and Linux packages #132.
  • Keep tauri-plugin-updater checking releases/latest/download/latest.json (already wired; check_for_update already runs on startup).
  • Ship a release whose artifacts that key actually signed. Until then the plugin correctly refuses every update, which is safer than installing an unsigned one.

WindowPet's updater shape is MIT. Attribution is already in the README.

Out of scope

Acceptance criteria

  • A packaged build finds an update on GitHub Releases, downloads, and installs it.
  • Unsigned or placeholder-key updates are refused.
  • The user does not have to track releases by hand.

Tests

Manual against a GitHub Release produced by #132.


Spec: docs/SPEC.md user story 71 · split from #18 · blocked on #132

Activity

  1. moved this from Todo to Ice Box in Fidgeton Sep 3, 2026
  2. modified the milestones: V1, V2 on Sep 6, 2026
  3. added
    p1Next up: the default for work that should happen
    on Sep 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestp1Next up: the default for work that should happenready-for-agentFully specified, ready for an AFK agent

    Projects

    • Status
      Ice Box

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions