The Version page lets you choose which build channel Synconix follows for updates. Pick the tier that fits your risk profile, and we’ll align the update repository to that channel.

Who can change this

Users must have both view_version_tier_page and change_version_tier permissions. Without the latter, the radio buttons are disabled.

Tiers at a glance

STABLE — recommended for production

Thoroughly tested, feature-frozen series intended for reliability.

RELEASE — mainstream/RC channel

Code-complete builds with the newest fixes and features that are nearing stable. Good for staging or early adopters.

BETA — bleeding-edge (test only)

Fast-moving development builds. Expect rough edges; not advised for production.

What the switch does

• Changes your update feed to the selected tier and records your preference.
• Future updates will pull from that tier (respecting your Auto Updates setting in Settings → General).
• If Auto Updates is on, new builds in that tier install automatically; if off, you’ll stay pinned until you update manually.

Version numbers shown

The cards display the latest available version per tier (Stable, Release, Beta). Your current installed version is compared to these to prevent mistakes.

Safety rails (downgrade prevention)

You can switch tiers only if the target tier’s latest version is equal or newer than your current version. Downgrades are blocked to avoid breaking changes.

Recommended workflows

• Production: Stable, Auto Updates on (or off with a scheduled manual update window).
• Staging/UAT: Release to preview incoming changes.
• Labs/Testing: Beta for feature validation.

After switching tier

• No immediate reboot is required, but a short repository refresh may occur.
• If Auto Updates are enabled, the system will pick up the next build from the new tier automatically when it’s available.
• If Auto Updates are disabled, plan a manual update at your convenience.

Troubleshooting

• Can’t select a tier: your role lacks change_version_tier.
• “Unable to change tier” warning: you tried to downgrade below your current version. Switch to a tier whose latest version is the same or newer, then update forward.
• No updates arriving: verify tier selection here and the Auto Updates toggle in Settings; check outbound network access to the update repo; review logs for update messages.

Good practices

• Mirror your production tier in a staging instance first and burn-in updates before promoting to prod.
• Document who is allowed to change tiers and when (change control).
• Keep regular backups and test restores before major jumps between versions or tiers.