Passbolt 5.4.0 ships with encrypted metadata and the accompanying new resource types promoted to stable. These capabilities have been battle-tested for months, and the most remaining edge cases have been smoothed out so they can now be enabled for everyone. Removing the beta label means that every new instance starts with encrypted metadata activated by default. As a result, features introduced in previous releases, such as icons, multiple URIs and custom fields, are available from day one without any action from end-users. For existing instances, the activation process has been simplified: administrators can decide with a single click whether their organisation is ready or would prefer to postpone the launch. Once enabled, the instance immediately supports the new resource types and their extended capabilities. Because the change may disrupt external integrations, existing content is not migrated automatically, migration remains the responsibility of content owners or administrators. It can be performed item-by-item by users in the main workspace or organisation-wide with the resource-metadata administration migration tool. Revisiting resource capabilities was also an opportunity to increase the maximum size of secret notes to 50 000 characters, leaving ample room for full certificate chains, keys of any flavour or any long text you need to keep encrypted. This release further improves cryptographic performance by introducing elliptic-curve keys (Curve25519/Ed25519) for new users. These keys provide security comparable to RSA-3072 while significantly reducing processing time and payload size. Performance has been tuned for large organisations that manage substantial numbers of users or resources. Among other improvements: Users' workspace now opens more quickly, and deleting multiple resources generates fewer I/O operations. Czech joins the list of supported languages, allowing native speakers to use Passbolt entirely in their own words, vítejte! Many thanks to everyone who reported issues and tested encrypted metadata over the past months. Your feedback made this release possible and brings these new features to all users today. Added

PB-44201: E2EE The organisation settings offer now a simplified way to activate metadata encryption and the new resource types
PB-42205: E2EE encrypted metadata and new resource types are activated by default after the first administrator setup
PB-43255: Add support for multiple uri import export on kdbx files
PB-43110: ZK - WP4.2 As a signed-in user I should not be allowed to upgrade resources with missing key situation
PB-43712: Translate the application in Czech
PB-43939: ZK - WP3.2 Add an app event to get or find the metadata keys settings
PB-43980: Add support for custom field import export on kdbx files
PB-44080: ZK - WP4.1 Create a dialog explaining the missing key situation ...