1.21.0-rc.0

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 same network detection for clients and sites, so connection don’t relay when they are on the same network (requires updated clients and sites)
• Add option to associate an access token (share link) to a specific account user
• Add optional access token (share link) session persistence when access token is passed via a query parameter or a header, so they don't have to passed on every request
• Add remember last used IdP and mark as last used
• Add enabled toggle to private resources
• Add pending resource state to resources created on a pending site via a provisioning key and provisioning blueprint
• Add clean up pending resources if reject pending site
• Add site provisioning key routes to integration API
• Fix improper query param encoding for email addresses preventing + characters in emails
• Dependency security updates
• General UI improvements
• Various other bug fixes

Full Changelog: 1.20.0...1.21.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.

View documentation