mirror of
https://github.com/vrtmrz/obsidian-livesync.git
synced 2026-11-01 13:58:18 +00:00
Archive older release notes for 1.0.43
This commit is contained in:
vorotamoroz committed
1 parent
349f5bb450
commit
f00d09e91e
2 files changed
+59
-59
No files matched your search
@@ -2,6 +2,65 @@
|
||||
|
||||
This document contains earlier published releases from the 1.0 line of the [current Self-hosted LiveSync release history](../../updates.md). Beta and release-candidate builds published before 1.0.0 are recorded in the [1.0 preview history](1.0-previews.md). Earlier release lines continue in the [0.25 history](0.25.md) and the [legacy history](legacy.md).
|
||||
|
||||
## 1.0.37
|
||||
|
||||
16th October, 2026
|
||||
|
||||
### Security
|
||||
|
||||
- Fixed an issue where synchronised changes could reach files outside the intended synchronisation scope under certain conditions. Updating is recommended.
|
||||
|
||||
### CLI
|
||||
|
||||
#### Fixed
|
||||
|
||||
- We can edit files through the CLI without resetting their creation time where the filesystem supplies it. (#1243)
|
||||
- Filesystems without birth-time support retain the existing change-time fallback. File replacement and restoration of a synchronised creation time remain subject to filesystem limitations.
|
||||
- `p2p-host` restores configured P2P automatic synchronisation, following, and change announcements after initialisation. (#1247)
|
||||
- Headless peer acceptance follows the configured policy. Single-operation commands retain their automatic synchronisation suspension.
|
||||
- We can select CLI-only Docker patches by their full release tag, such as `1.0.36-patch1-cli`, while keeping the Obsidian plug-in version.
|
||||
- Patch and RC images receive version and SHA-qualified tags. The `latest` and major-minor tags remain reserved for ordinary stable releases.
|
||||
|
||||
### Acknowledgements
|
||||
|
||||
Thank you for your contributions!
|
||||
|
||||
- @kimjansheden, for reporting the issue and contributing the fix and regression tests.
|
||||
|
||||
## 1.0.36
|
||||
|
||||
13th October, 2026
|
||||
|
||||
### Configuration Encryption
|
||||
|
||||
#### Fixed
|
||||
|
||||
- We can change the protection of sensitive configuration with Apply and keep our saved settings readable after a restart. (#1238, #1245)
|
||||
- The selected protection mode and passphrase are saved together. If Apply fails, our edits remain available to retry.
|
||||
- We can enter a missing or unusable custom configuration passphrase at start-up to unlock our protected settings. (#1239, #1245)
|
||||
- Cancelling the recovery dialogue preserves the encrypted configuration and stops that start-up attempt. Headless command-line start-up cannot complete the dialogue when recovery input is required.
|
||||
|
||||
### Localisation
|
||||
|
||||
#### Fixed
|
||||
|
||||
- We can read more settings, maintenance controls, and Fast Setup instructions in Spanish. (#1213, #1214)
|
||||
- Remote database lock warnings now use the existing translations consistently.
|
||||
- Fast Setup follows the selected display language while preserving saved choices across restarts and language changes.
|
||||
- We can read more settings, setup instructions, and messages in Simplified Chinese. (#1242)
|
||||
|
||||
### Maintenance
|
||||
|
||||
- Development tooling now uses compatible dependency versions with available security fixes. (#1245)
|
||||
- Repository-owned build and import alias helpers remove the vulnerable `braces` dependency.
|
||||
|
||||
### Acknowledgements
|
||||
|
||||
Thank you for your contributions!
|
||||
|
||||
- @zeedif (#1213, #1214)
|
||||
- @lingting0 (#1242)
|
||||
|
||||
## 1.0.35
|
||||
|
||||
5th October, 2026
|
||||
|
||||
-59
@@ -232,62 +232,3 @@ I have been finding troubleshooting difficult, so I decided to go back to basics
|
||||
### Maintenance
|
||||
|
||||
- The Review Harness can compare SHA-256 and xxHash64 file-content hashing on the current device, with fixed inputs from 4 KiB to 50 MiB and separate initialisation and warm-up measurements.
|
||||
|
||||
## 1.0.37
|
||||
|
||||
16th October, 2026
|
||||
|
||||
### Security
|
||||
|
||||
- Fixed an issue where synchronised changes could reach files outside the intended synchronisation scope under certain conditions. Updating is recommended.
|
||||
|
||||
### CLI
|
||||
|
||||
#### Fixed
|
||||
|
||||
- We can edit files through the CLI without resetting their creation time where the filesystem supplies it. (#1243)
|
||||
- Filesystems without birth-time support retain the existing change-time fallback. File replacement and restoration of a synchronised creation time remain subject to filesystem limitations.
|
||||
- `p2p-host` restores configured P2P automatic synchronisation, following, and change announcements after initialisation. (#1247)
|
||||
- Headless peer acceptance follows the configured policy. Single-operation commands retain their automatic synchronisation suspension.
|
||||
- We can select CLI-only Docker patches by their full release tag, such as `1.0.36-patch1-cli`, while keeping the Obsidian plug-in version.
|
||||
- Patch and RC images receive version and SHA-qualified tags. The `latest` and major-minor tags remain reserved for ordinary stable releases.
|
||||
|
||||
### Acknowledgements
|
||||
|
||||
Thank you for your contributions!
|
||||
|
||||
- @kimjansheden, for reporting the issue and contributing the fix and regression tests.
|
||||
|
||||
## 1.0.36
|
||||
|
||||
13th October, 2026
|
||||
|
||||
### Configuration Encryption
|
||||
|
||||
#### Fixed
|
||||
|
||||
- We can change the protection of sensitive configuration with Apply and keep our saved settings readable after a restart. (#1238, #1245)
|
||||
- The selected protection mode and passphrase are saved together. If Apply fails, our edits remain available to retry.
|
||||
- We can enter a missing or unusable custom configuration passphrase at start-up to unlock our protected settings. (#1239, #1245)
|
||||
- Cancelling the recovery dialogue preserves the encrypted configuration and stops that start-up attempt. Headless command-line start-up cannot complete the dialogue when recovery input is required.
|
||||
|
||||
### Localisation
|
||||
|
||||
#### Fixed
|
||||
|
||||
- We can read more settings, maintenance controls, and Fast Setup instructions in Spanish. (#1213, #1214)
|
||||
- Remote database lock warnings now use the existing translations consistently.
|
||||
- Fast Setup follows the selected display language while preserving saved choices across restarts and language changes.
|
||||
- We can read more settings, setup instructions, and messages in Simplified Chinese. (#1242)
|
||||
|
||||
### Maintenance
|
||||
|
||||
- Development tooling now uses compatible dependency versions with available security fixes. (#1245)
|
||||
- Repository-owned build and import alias helpers remove the vulnerable `braces` dependency.
|
||||
|
||||
### Acknowledgements
|
||||
|
||||
Thank you for your contributions!
|
||||
|
||||
- @zeedif (#1213, #1214)
|
||||
- @lingting0 (#1242)
|
||||
Reference in new issue
Block a user