0.25.41-patched-1
- 29th January, 2026
Yes, I have changed my mind. Let's release the beta version...
We have set up the CI environment too. You know, naturally, the current CI is still in the foundational stage with mocked harness and checks quite the basic features; merely exists, for now, so I am eagerly awaiting your contributions.
Schemes for beta releases:
- Beta versions are denoted by appending
-patched-Nto the base version number.The base versionmostly corresponds to the stable release version.- e.g., v0.25.41-patched-1 is equivalent to v0.25.42-beta1.
- This notation is due to SemVer incompatibility of Obsidian's plugin system.
- Hence, this release is
0.25.41-patched-1.
- Each beta version may include larger changes, but bug fixes will often not be included.
- I think that in most cases, bug fixes will cause the stable releases.
- They will not be released per branch or backported; they will simply be released.
- Bug fixes for previous versions will be applied to the latest beta version.
This means, if xx.yy.02-patched-1 exists and there is a defect in xx.yy.01, a fix is applied to xx.yy.02-patched-1 and yields xx.yy.02-patched-2.
If the fix is required immediately, it is released as xx.yy.02 (with xx.yy.01-patched-1). - This procedure remains unchanged from the current one.
- At the very least, I am using the latest beta.
- However, I will not be using a beta continuously for a week after it has been released. It is probably closer to an RC in nature.
In short, the situation remains unchanged for me, but it means you all become a little safer. Thank you for your understanding!
Refactored
WebPeerhas been moved to the main repository from the sub repositorylivesync-commonlibfor correct dependency management.- Migrated from the outdated, unstable platform abstraction layer to services.
- A bit more services will be added in the future for better maintainability.