Join the Beta Channels
Mindwtr publishes beta and release-candidate builds before the final stable release. Betas get new features and bug fixes earlier, and they help catch platform-specific issues before the same build reaches everyone on stable.
You can stay on a beta channel long term. Stable releases are also published to the beta channels, so beta testers do not need to switch back after a test cycle just to stay current.
If you need the lowest-risk build, use the stable installation pages instead:
Android - Google Play Open Testing
Join the Google Play open testing track, then update through the Play Store as normal:
To leave the beta later, return to the same testing link and choose Leave the test.
iOS, iPadOS, and macOS - TestFlight
Install TestFlight, then join the Mindwtr beta:
To leave TestFlight, remove Mindwtr from TestFlight and reinstall the stable version from the App Store or Mac App Store.
Linux - AUR Beta
Arch Linux and derivative users can install the dedicated beta package:
yay -S mindwtr-bin-betaPackage page:
To go back to stable, install mindwtr-bin instead.
Linux - Flathub Beta
Add the Flathub beta remote once, then install the beta branch:
flatpak remote-add --if-not-exists flathub-beta https://flathub.org/beta-repo/flathub-beta.flatpakrepo
flatpak install flathub-beta tech.dongdongbh.mindwtr//betaRun the beta build explicitly:
flatpak run --branch=beta tech.dongdongbh.mindwtrYou can keep stable and beta installed side by side. To make the desktop launcher open the beta branch:
flatpak make-current tech.dongdongbh.mindwtr betaTo switch the launcher back to stable later:
flatpak make-current tech.dongdongbh.mindwtr stableLinux - APT and RPM Beta Repos
Debian and Ubuntu users can add the beta APT repo (the signing key is shared with the stable repo):
curl -fsSL https://dongdongbh.github.io/Mindwtr/mindwtr.gpg.key | sudo gpg --dearmor -o /usr/share/keyrings/mindwtr-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/mindwtr-archive-keyring.gpg] https://dongdongbh.github.io/Mindwtr/deb-beta ./" | sudo tee /etc/apt/sources.list.d/mindwtr-beta.list
sudo apt update
sudo apt install mindwtrFedora, RHEL, and openSUSE users can add the beta DNF/YUM repo:
cat <<'EOF' | sudo tee /etc/yum.repos.d/mindwtr-beta.repo
[mindwtr-beta]
name=Mindwtr Beta Repository
baseurl=https://dongdongbh.github.io/Mindwtr/rpm-beta
enabled=1
gpgcheck=0
EOF
sudo dnf install mindwtrStable releases are published to the beta repos too. Release candidates are versioned as 1.2.0~rc.3 in the package metadata, which both APT and DNF sort below the final 1.2.0, so regular upgrades move you from a release candidate to the matching stable build automatically.
To leave the beta repo, remove /etc/apt/sources.list.d/mindwtr-beta.list (or /etc/yum.repos.d/mindwtr-beta.repo) and reinstall from the stable repo.
Docker - Beta Tag
Every release lands on GHCR with its version tag, and the floating beta tag always points at the newest release (release candidate or stable), so beta users never switch tags. latest stays on the newest stable release:
docker pull ghcr.io/dongdongbh/mindwtr-app:beta
docker pull ghcr.io/dongdongbh/mindwtr-cloud:betaA specific pre-release can be pinned by version, for example ghcr.io/dongdongbh/mindwtr-app:1.2.0-rc.1. See Docker Deployment for compose setup.
Windows, AppImage, FOSS APK, and Other Direct Downloads
Pre-release builds are published on GitHub Releases and marked as pre-release:
Look for versions with a pre-release suffix such as -rc or -beta. Stable releases are still available from the same page.
Reporting Beta Issues
If you hit a bug, please open an issue and include:
- your platform
- the version from Settings -> About
- what you expected to happen
- what happened instead
Beta feedback is most useful when it includes the platform and exact version, because release-candidate fixes often vary by channel.