Updates and Versions

Updates and Versions

Versioning. Releases are MAJOR.MINOR.PATCH-beta.N: the base comes from package.json and N is the CI build number, so every release is a pre-release and each is newer than the last (0.2.0-beta.7 > 0.2.0-beta.6). Bump the base by hand for a new minor or major. The in-app update check follows the beta series.

Choosing when updates happen

In Setup > SYSTEM the Update policy setting offers:

• BEFORE APP OPENS — INSTALL AUTOMATICALLY: check and install first, then open the full app
• AFTER APP OPENS — INSTALL WHEN I QUIT
• AFTER APP OPENS — ASK WHEN READY
• ONLY WHEN I ASK: use the CHECK NOW button
• NEVER

HELP > WHAT'S NEW lists what changed in each release. If an update fails or the network is down, RerunTV carries on normally.

Your data is kept

Your channels and settings live in the userData folder next to the app, and a backup is taken before an update installs, so an update keeps your lineup. Some plugins are renamed between releases; your settings and approvals for them are carried over automatically, though a plugin whose permissions changed may ask you to approve it once.

Checking a download

Releases are built by this repository's CI and are not code-signed yet. See Installation for why Windows warns and how to verify an installer with the checksum file or the GitHub attestation. Every release lists its files on the Releases page.

Release assets

Each release has the installer (RerunTV-Setup-<version>.exe), its blockmap and latest.yml (what the in-app updater reads), and SHA256SUMS.txt.

See also Security.