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 additional DNS records on pangolin delegated domains in Pangolin DNS mode
- Add optional match on base wildcard domains
- Add revalidate OIDC sessions with the IdP using refresh tokens
- Add SSH session logging
- Add resource session management
- Add opt-in CrowdSec bot detection
- Fix failing Safari passkey registration
- Fix the enabled/disabled filter on the private resources table
- Fix order same-second status events in status history
- Fix duplicate header auth from blueprints
- Fix swagger missing from container build
- Fix missing API key permissions for integration API routes
- Dependency updates
New Contributors
- @jnko266 made their first contribution in #3938
- @ASPCODES made their first contribution in #3988
- @samirasidd made their first contribution in #3971
- @RishavTiwari25 made their first contribution in #3999
- @S-NoF3aR made their first contribution in #4027
Full Changelog: 1.25.3...1.26.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.