UUPD 2.0.0-beta.1 is now available, with a focus on making stable and pre-release updates easier to manage.
This release adds better support for projects that ship alpha, beta, RC, or dev builds alongside stable releases.
What’s new:
- New
release_channel support
- Support for
stable, dev, alpha, beta, rc, and prerelease channels
- Update requests now include
allow_prerelease and release_channel
- Static JSON metadata can now include both stable and pre-release details
- UUPD can choose the right update track based on client configuration
- Pre-release updates only apply when enabled and newer than the stable version
- Release-channel cache keys help prevent stable and pre-release metadata collisions
- Manual update checks now clear all channel-specific caches
Why this matters:
You can now publish a stable release and a newer beta or alpha release at the same time, while keeping stable users on the stable track.
Users who have pre-release updates enabled can receive the newer test build, while everyone else continues to receive the latest stable version.
This is especially useful for private update servers, static index.json files, GitHub-hosted assets, and staged testing workflows.
If you are already testing UUPD 2.0, beta.1 is a good release to test against your real update flow before the final 2.0 release.
