Merged
Conversation
Two issues prevented Bear from recognizing edits made via the CLI: 1. Vector clock was being replaced instead of updated - incrementVectorClock created a new clock with only "Bear CLI", discarding all other device entries. Bear uses the vector clock to track changes across devices, so losing entries caused it to misinterpret the update. Now uses PropertyListSerialization to properly parse, preserve all device entries, and only increment the "Bear CLI" counter. 2. Text asset field not cleared on edit - when a note stored its content as an external asset (text field with downloadURL), the CLI wrote new content to textADP but left the old asset reference intact. Bear may read from the asset instead of textADP. Now explicitly sets text to null on update. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Fix Bear app not detecting note changes from CLI
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The release workflow now injects the version from the git tag into the source before building, ensuring the binary always reports the correct version regardless of what is hardcoded in Exports.swift.
asabirov
pushed a commit
that referenced
this pull request
Apr 8, 2026
Surface per-record CloudKit errors from modify operations
asabirov
added a commit
that referenced
this pull request
Apr 8, 2026
Pass git tag version to Go ldflags so release binaries report correct version. (reimplements PR #7)
asabirov
added a commit
that referenced
this pull request
Apr 8, 2026
Pass git tag version to Go ldflags so release binaries report correct version. (reimplements PR #7)
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
1 participant
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.
Summary
softprops/action-gh-releasedoes not overwrite existing assets — if a release was created manually with a stale binary first, the CI-built binary upload was silently skippedGITHUB_REF_NAME) intoExports.swiftbefore building, so the binary always matches the tag regardless of what's hardcoded in sourceTest plan
v0.3.5-test) and verify the workflow sets the correct version in the built binarybcli --versionoutput matches the tag