Skip to content

Installer says auto-updates are enabled after an upgrade when they are actually off #476

Description

@artemiia

After upgrading, the installer told me auto-updates were enabled. They weren't, and the CLI says so.

Environment: macOS 15 (Darwin 24.5, arm64), node upgraded from a March v1.2.x build to v1.13.10 via curl -fsSL https://pilotprotocol.network/install.sh | sh on 2026-09-24. Daemon managed by launchd.

What happened
Installer output ended with:

Service: network.pilotprotocol.pilot-updater (auto-updates)
Started: pilot-updater (auto-updates enabled)

Seconds later ~/.pilot/updater.log:

level=INFO msg="auto-update disabled; loop idle until enabled" state_path=/Users/macmini/.pilot/auto-update.json

and pilotctl update status → Automatic updates: disabled.

Cause
install.sh only writes {"enabled": true} to ~/.pilot/auto-update.json when $UPDATING != true (line ~1721), i.e. on a fresh install. The upgrade path still prints "auto-updates enabled" (line ~2050, and the systemd equivalent at ~1848). An upgraded node that never had the file ends up with the loop running but idle.

Expected
Either write the enable file on upgrade too (the comment at line ~1837 says this is the intent: "the consent block above both tell the operator auto-updates are ON"), or print the actual state.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions