0.25.7
15th August, 2025
Since the release of 0.25.6, there are two large problem. Please update immediately.
- We may have corrupted some documents during the migration process. Please check your documents on the wizard.
- Due to a chunk ID assignment issue, some data has not been encrypted. Please rebuild the database using Rebuild Everything if you have enabled E2EE.
So, If you have enabled E2EE, please perform Rebuild everything
. If not, please check your documents on the wizard.
In the next version, insecure chunk detection will be implemented.
Fixed
- Off-loaded chunking has been fixed to ensure proper functionality (#693).
- Chunk document ID assignment has been fixed.
- Replication prevention message during version up detection has been improved (#686).
Keep A
andKeep B
on Conflict resolving dialogue have been renamed toUse Base
andUse Conflicted
(#691).
Improved
- Metadata and content-size unmatched documents are now detected and reported, preventing them from being applied to the storage.
- This behaviour can be configured in
Patch
->Edge case addressing (Behaviour)
->Process files even if seem to be corrupted
- Note: this toggle is for the direct-database-manipulation users.
- This behaviour can be configured in
New Features
Scan for Broken files
has been implemented onHatch
->TroubleShooting
.
Refactored
- Off-loaded processes have been refactored for better maintainability.
- Files prefixed
bg.worker
are now working on the worker threads. - Files prefixed
bgWorker.
are now also control tof hese worker threads. (I know what you want to say... I will rename them).
- Files prefixed
- Removed unused code.