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.
What's Changed
Note
Some things like fingerprinting and posture info coming in new clients as they are released. Please update clients when released to test.
- Add store user device fingerprint information (OS, serial number, hostname, etc)
- Add store user device posture information (auto updates, encryption, biometrics, etc) (EE)
- Add user device approvals for admins; explicitly approve a user’s device before it can connect to resources (EE)
- Add support for organization only scoped identity providers for true multi-tenancy (EE)
- Add block user device and machine
- Add archive user device and machine client
- Add show Site and Client install commands on credentials tab
- Add option to set rule priorities in blueprints
- Add Russian, Bulgarian, and Czech languages
- Fix logo URL optional in custom org branding (EE)
- Fix confirm delete button working without confirm text
- General UI improvements
- Various other bug fixes
New Contributors
- @ruxenburg made their first contribution in #2172
- @JackMyers001 made their first contribution in #2204
- @K0lin made their first contribution in #2273
- @JanGrosse made their first contribution in #2209
Full Changelog: 1.14.1...1.15.0-rc.0
How to Update
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.