RC
A Release Candidate (RC) is a near-final software version, stable but undergoing last tests before official release. It has all features and no known bugs.
- Users: Use cautiously due to potential undiscovered bugs. Not for critical systems unless prepared for issues. Report bugs.
- Developers/Testers: Perform crucial final validation and thorough testing, especially of recent changes, to catch last-minute major issues.
- Backup: Always back up data before installing an RC to allow rollback if problems arise.
- Feedback: Provide feedback; it's vital for a robust final release.
Note
Keep a backup of the last stable database as you will be unable to update from a RC to the next stable version. Database migrations may change between release candidates and stable versions.
What’s Changed
- Add redirects
- Add mTLS support for public resources (EE)
- Add support for assigning roles to machines
- Add export blueprint functionality for all resources
- Add labels to the integration API
- Add support for configuring load balancing strategy
- Add client identities to Pangolin Sites for Remote- headers on private HTTP
- Add offline checking intervals configuration
- Add site, machine client, and remote node credential regeneration to CE
- Improve image size by pruning stuff and things
- Fix cluster license registration
- Fix Integration API organization delete
- Fix allow underscores in health check hostnames
- Fix pass relay port to Gerbil
- Fix avoid exponential backtracking in isPathAllowed
- Fix ensure more than 1 parts exists in signup page
- Fix send missing error when clients registering
- Fix clean up every site when deleting an org
- Fix prevent overlapping exit node address selections
- UI improvements
Full Changelog: 1.24.0...1.25.0-rc.0
New Contributors
- @kdcokenny made their first contribution in #3838
- @mr-pmillz made their first contribution in #3830
- @TiltedTeapot made their first contribution in #3870
- @choksi2212 made their first contribution in #3895
How to Update
Important
For all load balancing options to work, Treafik version 3.6 or greater must be used in your stack. Update accordingly.
Important
Redirects will work on older versions of Badger. In order to enable permanent redirects, update Badger to v1.8.0 or greater. The migration will automatically do this if it can find the Traefik config in the standard location. Otherwise, please ensure your Badger is up to date manually.
Important
Always back up your config app-data before updating. This will allow you to easily roll back if the update breaks your configuration. You will not be able to easily downgrade otherwise.