v1.16.0 — schedules that wait for an empty server, and Conan updates that stick

This release's image never published, so latest stayed on v1.15.0. Everything below ships in v1.17.0.

Six changes since v1.15.0. @magnuspihl added held player-count conditions, and reports from @jdvieira and @odogscorner-lgtm led to two of the fixes. Thanks to all three.

Schedules can wait for an empty server

A "stop when nobody is online" schedule only looked at the player count at the moment it fired. If the server had started a minute earlier, nobody had time to join, and it got stopped. Under the player-count picker there's now an "…and this has been true for X minutes" checkbox, from 1 to 60 minutes, on server and global schedules.

The window only counts time since the server last reached Running, so a restart starts it over. If there isn't enough history yet, because the server just started or the manager restarted, that firing is skipped. A game that can't report a player count still runs once it's been up long enough.

A stop schedule on a server that's already stopped or crashed is now skipped instead of logged as an error. An "all servers" stop used to send one failure webhook per idle server, after taking a backup and running the player countdown for nothing. Start schedules skip a server that's already running the same way. A server that's Installing or Updating still fails and notifies, as before.

Conan Exiles

• Update game installs the new build again. The current Conan image rejects the update-check interval Palisade passed, so the update boot crashed, the retry came back on the old build, and the badge stayed lit. Palisade now passes 24 hours, the most the image accepts. So a server booted by Update game that stays up longer than a day can pick up the next Conan build in place, after the image's 30-minute RCON warning. The next normal start turns that off again.
• A PvP or raid schedule with only some of its days, start and end filled in is refused when you save. Older Conan images crashed on every boot with a partial schedule, and the current one drops it, so the schedule never runs. Leaving all three blank is still fine.
• A TARGET_MANIFEST_ID pin no longer updates Conan on every boot. The Conan image never reads that variable, so the "pin" switched on its updater and fetched the latest build at each start. It also overrode an explicit AUTO_UPDATE=false, which now holds.

Updates

• The "Update available" badge clears as soon as an updated server reaches Running, not at the next 3-hourly check. An open page refreshes on its own, and notification targets subscribed to "Installs finished" get a message.
• TARGET_MANIFEST_ID only applies to native Palworld, the one image that honours it. On Palworld Wine a pin forced an update to the latest build on every start. The variable is now ignored there, and the env-vars card only suggests it for native Palworld.

Before you upgrade

This release adds a database migration. Prisma only migrates forward, so rolling back to v1.15.0 needs a database backup from before the upgrade. Palisade snapshots its database nightly, under Settings → Backups.