Prepare v0.3.0 personal testing release - #41
Merged
Merged
Conversation
oshtz
marked this pull request as ready for review
September 5, 2026 10:39
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepare v0.3.0 for personal testing on Windows and macOS. This combines bundled 7-Zip archive support, Finder-style column activation and selection fixes, folder view-state persistence, and opt-in executable Syncthing, Git, and Obsidian plugins with native settings/onboarding and platform packages.
Includes the current v0.2.16 main-branch fixes. App and official plugin versions agree at 0.3.0. Release output remains a draft; repository transfer and version reset are future work.
Validation: 420 workspace tests passed (7 ignored), strict workspace clippy, formatting, workspace check, 28 packaging/workflow tests, and dependency audits passed under the existing audit policy. Platform CI and release packaging must pass before the version tag is created.
Draft plugin assets require authenticated download and developer loading for personal testing; official catalog installation and real-machine attestations remain separate checks before public publication. See docs/plugins.md for the draft testing procedure.