Daemon Support Lifecycle
How long each daemon version is supported, how sunset dates are set, and what changes at each stage.
Scanopy supports a rolling window of daemon versions. Older versions move through a predictable lifecycle before support ends, and you are notified well before a daemon stops working.
Lifecycle stages
Every daemon has exactly one version status, shown as a tag next to its name (see Daemon Status):
| Stage | What it means | What changes for you |
|---|---|---|
| Current | On the newest release line | Nothing |
| Outdated | Supported, but a newer version exists | Optional upgrade at your convenience |
| Deprecated | A sunset date is scheduled for this version | The daemon still works; you see the date and a countdown, and receive an email. Upgrade before the date |
| Unsupported | Past its sunset date | The server rejects the daemon; it cannot connect or run discovery until updated |
| Unknown | The server has no recorded version | Report a version by running a current release; treated as unsupported once a floor is enforced |
How sunset dates are set
Sunset dates are not hand-typed constants that can silently expire. Each release carries a table of its shipped versions and their dates, and the supported window is derived from that table plus the current date. A server only ever enforces a floor its own version can account for, so a self-hosted server that is pinned to an old release will never reject a daemon of its own generation.
When a sunset is scheduled, the date is published by the server and used identically everywhere it appears — the daemon card, the upgrade dialog, and the notification email all show the same date.
Support window
- The current release line and the previous two minor lines are supported.
- A line is supported for at least 6 months after the release that superseded it.
Whichever is longer applies. In practice this is roughly a six-month window given Scanopy's release cadence.
How you are notified
- In the app: a Deprecated or Unsupported daemon shows a colored status tag, and its card and upgrade dialog show the sunset date and a countdown. A banner appears on the Daemons view while any daemon needs updating.
- By email: when a sunset is announced, the organization owner and each affected daemon's maintainer receive one email listing every affected daemon and the date. You are not emailed again for the same sunset.
What to do
Upgrade affected daemons before their sunset date — see Managing Daemons for per-platform steps. Upgrading preserves all configuration, and an Unsupported daemon reconnects automatically once updated.