mirror of
https://github.com/vrtmrz/obsidian-livesync.git
synced 2025-12-12 17:25:56 +00:00
bump
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"id": "obsidian-livesync",
|
||||
"name": "Self-hosted LiveSync",
|
||||
"version": "0.25.24",
|
||||
"version": "0.25.25",
|
||||
"minAppVersion": "0.9.12",
|
||||
"description": "Community implementation of self-hosted livesync. Reflect your vault changes to some other devices immediately. Please make sure to disable other synchronize solutions to avoid content corruption or duplication.",
|
||||
"author": "vorotamoroz",
|
||||
|
||||
4
package-lock.json
generated
4
package-lock.json
generated
@@ -1,12 +1,12 @@
|
||||
{
|
||||
"name": "obsidian-livesync",
|
||||
"version": "0.25.24",
|
||||
"version": "0.25.25",
|
||||
"lockfileVersion": 2,
|
||||
"requires": true,
|
||||
"packages": {
|
||||
"": {
|
||||
"name": "obsidian-livesync",
|
||||
"version": "0.25.24",
|
||||
"version": "0.25.25",
|
||||
"license": "MIT",
|
||||
"dependencies": {
|
||||
"@aws-sdk/client-s3": "^3.808.0",
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "obsidian-livesync",
|
||||
"version": "0.25.24",
|
||||
"version": "0.25.25",
|
||||
"description": "Reflect your vault changes to some other devices immediately. Please make sure to disable other synchronize solutions to avoid content corruption or duplication.",
|
||||
"main": "main.js",
|
||||
"type": "module",
|
||||
|
||||
30
updates.md
30
updates.md
@@ -4,6 +4,36 @@ Since 19th July, 2025 (beta1 in 0.25.0-beta1, 13th July, 2025)
|
||||
|
||||
The head note of 0.25 is now in [updates_old.md](https://github.com/vrtmrz/obsidian-livesync/blob/main/updates_old.md). Because 0.25 got a lot of updates, thankfully, compatibility is kept and we do not need breaking changes! In other words, when get enough stabled. The next version will be v1.0.0. Even though it my hope.
|
||||
|
||||
## 0.25.25
|
||||
|
||||
06th November, 2025
|
||||
|
||||
### Fixed
|
||||
|
||||
#### JWT Authentication
|
||||
|
||||
- Now we can use JWT Authentication ES512 correctly (#742).
|
||||
- Several misdirections in the Setting dialogues have been fixed (i.e., seconds and minutes confusion...).
|
||||
- The key area in the Setting dialogue has been enlarged and accepts newlines correctly.
|
||||
- Caching of JWT tokens now works correctly
|
||||
- Tokens are now cached and reused until they expire.
|
||||
- They will be kept until 10% of the expiration duration is remaining or 10 seconds, whichever is longer (but at a maximum of 1 minute).
|
||||
- JWT settings are now correctly displayed on the Setting dialogue.
|
||||
|
||||
And, tips about JWT Authentication on CouchDB have been added to the documentation (docs/tips/jwt-on-couchdb.md).
|
||||
|
||||
#### Other fixes
|
||||
|
||||
- Receiving non-latest revisions no longer causes unexpected overwrites.
|
||||
- On receiving revisions that made conflicting changes, we are still able to handle them.
|
||||
|
||||
### Improved
|
||||
|
||||
- No longer duplicated message notifications are shown when a connection to the remote server fails.
|
||||
- Instead, a single notification is shown, and it will be kept on the notification area inside the editor until the situation is resolved.
|
||||
- The notification area is no longer imposing, distracting, and overwhelming.
|
||||
- With a pale background, but bordered and with icons.
|
||||
|
||||
## 0.25.24
|
||||
|
||||
04th November, 2025
|
||||
|
||||
Reference in New Issue
Block a user