Menu β–Ύ β–΄

#388 feat(updates): choose how often to check, and show release notes

closed
nobody
None
2026-11-07
2026-11-07
Anonymous
No

Originally created by: kristofferR

Automatic update checks ran on a fixed four-hour schedule, and the update prompt only said that a new version existed, not what changed, before asking for consent to install.

Check frequency. Settings β†’ Advanced gains Check for updates: every hour, every 4 hours (default) or once a day. It is stored as update_check_hours (sanitized to those choices), the background loop reads it each cycle, and changing it restarts the schedule at once. The choice is disabled where automatic checks don't run (checks off, debug builds, Snap).

Release notes. When an update is offered, the Settings footer shows What's new in Carrier X with that release's own notes from the signed update, as plain text. The native command returns notes only while it still offers that exact version.

Safer refresh. When Settings regains focus, a new UpdateConsentController.refresh() re-reads the retained discovery: it shows a newer offer, or returns to "Check for updates" when the offer was cleared, so a cleared offer can never be installed by the next click. It never interrupts a check or install, including one that starts while it reads. Tests cover both.

Part of [#262]; the preview channel and rollback are still to come.

Ref [#262]

CodeRabbit reviews this change in the combined PR [#394].

Related

Tickets: #262
Tickets: #394

Discussion

  • Anonymous

    Anonymous - 2026-11-07

    Originally posted by: chatgpt-codex-connector[bot]

    Codex Review Summary: βœ… Completed This comment shows the latest Codex review activity on this pull request. | Review | Status | Commit | Review trigger | | --- | --- | --- | --- | | πŸ“ **Code Review** | βœ… **Completed** <relative-time datetime="2026-11-07T17:14:57.818831Z">2026-11-07T17:14:57.818831Z</relative-time> | `5f42e57` | Manual request |
    ℹ️ About Codex in GitHub
    [Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you - Open a pull request for review - Mark a draft as ready - Comment "@codex review" or "@codex security review". Codex reacts with πŸ‘€ while any review is running, comments if it has suggestions, and reacts with πŸ‘ once all reviews finish with no findings.
     
  • Anonymous

    Anonymous - 2026-11-07

    Originally posted by: chatgpt-codex-connector[bot]

    Codex Review: Didn't find any major issues. Chef's kiss.

    Reviewed commit: 5f42e578e7

    ℹ️ About Codex in GitHub
    [Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you - Open a pull request for review - Mark a draft as ready - Comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with πŸ‘. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
     
  • Anonymous

    Anonymous - 2026-11-07

    Originally posted by: kristofferR

    ⏸️ crq will not request further automated reviews for this pull request.

    Reason: CodeRabbit reviews these changes once, in combined PR [#394]

    Resume with crq unhold kristofferr/carrier 388.

     

    Related

    Tickets: #394

  • Anonymous

    Anonymous - 2026-11-07

    Ticket changed by: kristofferR

    • status: open --> closed
     
  • Anonymous

    Anonymous - 2026-11-07

    Originally posted by: kristofferR

    βœ… The administrative hold has been retired because this pull request merged. crq will not request further automated reviews.

     

Log in to post a comment.