Releases: tgdrive/teldrive
Releases · tgdrive/teldrive
1.6.11
1.6.10
1.6.9
Important
- This version drops support for duplicate files to keep consistency with common filesystems.Now particular file will be replaced with old one instead of throwing error.
- Replacing content will result in orphan file parts in a channel run
teldrive check --clean
to perform cleanup tasks on channels monthly or biweekly. - If this version fails in migration step make sure to run
rclone dedupe
with suitable policy to remove duplicates and rerun.
Changelog
Refactoring
Changelog
Refactoring
- 4202793: refactor: remove file duplication completely (@bhunter234)
1.6.8
Changelog
Features
- a3bb0ce: feat: add upgrade command for updating TelDrive (@divyam234)
Refactoring
- 8e4dfd8: refactor: add index for listing channel files and impove check command (@divyam234)
Others
- 303a2b6: chore(docs): update contributing guide (@divyam234)
1.6.7
Changelog
Features
- 0540ae1: feat: add new check command to check integrity of file parts (@bhunter234)
Refactoring
- 7b4fd14: refactor: improve command flag registration (@bhunter234)
1.6.6
Important
- Session storage now uses sqlite instead of bbolt and renamed to
storage.db
fromsession.db
- Delete old session file and recreate empty db file.
Changelog
Refactoring
- 0d51fdf: refactor: migrate session db from bbolt to sqlite (@bhunter234)
1.6.5
Changelog
Refactoring
- f0187f4: refactor: standardize field naming and improve cache key generation (@bhunter234)
- 4c5d503: refactor: update logging configuration to use string levels (@bhunter234)
1.6.4
Changelog
Refactoring
- 299f4fa: refactor: improve SQL query for uploads statistics with correct date handling (@bhunter234)
- 518435f: refactor: replace kv usage with boltdb and update related configurations (@bhunter234)
Others
- e966119: chore(build): update Makefile (@bhunter234)
1.6.3
Changelog
Bug fixes
- 381ea31: fix: take correct size in encrypted streams (@bhunter234)
Refactoring
- 7fa4a38: refactor: add version endpoint (@bhunter234)
- 3252c20: refactor: use latest timestamp for created_at (@bhunter234)