The beta channel

TrayTrigger updates itself from GitHub Releases. Stable releases go to everyone. Beta releases are marked as pre-releases on GitHub and are only offered to people who opt in here.

What you get

• New features and fixes before the stable release, usually days to weeks earlier.
• Builds that have had less testing. A beta can have a bug that a stable release would not.
• Version numbers such as v1.3.0-beta.2. The suffix tells you it is a beta and which one.

How versions are chosen

• With the toggle on, TrayTrigger looks at every release and offers the highest version, beta or stable.
• With the toggle off, it asks GitHub for the latest stable release only, and betas are invisible — unless the build you are running is itself a beta, in which case later betas are always offered regardless of the toggle. Otherwise a tester who installed a beta by hand would be stranded on it: GitHub keeps pre-releases out of "latest", so the only build ever offered would be the older stable, which loses the comparison and reports "up to date" forever.
• A stable release always outranks its own betas. When v1.3.0 ships, everyone on any v1.3.0 beta is offered it, toggle on or off.

Joining from a build you installed by hand

Installing a beta's Setup.exe does not tick the toggle for you. The build still follows later betas, as above, so you stay current either way — but tick it anyway if you want the beta channel to survive you moving back to a stable release later.

Leaving the beta channel

• Turn the toggle off. You keep the beta you have until the next stable release overtakes it, then update as normal. While you are on a beta, later betas keep arriving.
• To go back to stable immediately, install the current stable release from the GitHub Releases page over the top. Your library and settings are kept.

The repository field

The repository is where TrayTrigger looks for releases. Leave it at the default unless you are building TrayTrigger yourself from a fork.

---

Part of Updates. This page is the same text as the app's Learn more button, generated from Help/updates/prerelease.md. To fix something, edit that file (or open an issue); wiki edits are overwritten on the next sync.