Release OWD Sync 0.1.4 - #4
Merged
Merged
Conversation
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.
What changed
owd-pairprotocol handler before upstream plugin startup0.1.45406b5880613c716f5b398353da546160d483d59Why
The dashboard could open a syntactically valid
obsidian://owd-pairrequestwhile the matching handler was not loaded in the opened vault. The earlier
startup order also delayed handler registration until after upstream
initialization.
User impact
BRAT testers receive a new immutable plugin release that recognizes the pairing
handoff as soon as OWD Sync loads. The dashboard still provides a command-based
manual fallback if Obsidian opens a vault where the plugin is disabled.
Validation
pnpm check— formatting, lint, typecheck, 9 tests, build, production guardspnpm package— version-matched0.1.4ZIP and checksumsmain.jsis byte-for-byte identical to the monorepo candidate (9403c736df9642022a8255730a140df444f35e7e62d604828d7cc59420522f98)