v0.3.4

Fix: Bear app not detecting note changes from CLI

Two issues prevented the Bear app from recognizing edits made via the CLI:

1. Vector clock preserved instead of replaced
incrementVectorClock was creating a new clock with only a "Bear CLI" entry, discarding all other device entries (iPhone, iPad, Mac). 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 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, showing stale content. Now explicitly sets text to null on update.

What's Changed

• Fix Bear app not detecting note changes from CLI by @asabirov in #6

What's Changed

• Fix modification date not updating after note edit by @asabirov in #5

Full Changelog: v0.3.2...v0.3.4

v0.3.3

Fix: Modification date not updating after note edit

Fixed a bug where the Modified date shown in bcli ls was not updated after editing a note with bcli edit <id> --stdin (or other edit modes).

Root cause: The modified record-level metadata was passing through the old timestamp from the original record, causing CloudKit to not recognize the update. Now both updateNote() and trashNote() use the current timestamp for the modified metadata.

What's Changed

• Fix modification date not updating after note edit by @asabirov in #5

Full Changelog: v0.3.2...v0.3.3

v0.3.2

Bug fix

• Fix truncated record IDs in bcli ls and bcli todo table output. Swift's padding(toLength: 38) was silently chopping CloudKit record names longer than 38 characters. ID column width is now computed dynamically from the data.

Full Changelog: v0.3.1...v0.3.2

What's Changed

• Fix truncated record IDs in table output by @asabirov in #4

Full Changelog: v0.3.1...v0.3.2

v0.3.1

Bug fix

• Fix crash when bcli get is called with an ID that doesn't match a CloudKit record name. CloudKit's records/lookup can return records without a fields key, which caused a decoding error. Now handles missing fields gracefully and falls through to uniqueIdentifier search.

Full Changelog: v0.3.0...v0.3.1

What's Changed

• Extract BearCLICore library and add test infrastructure by @asabirov in #2
• Fix crash when CloudKit returns records without fields by @asabirov in #3

New Contributors

• @asabirov made their first contribution in #2

Full Changelog: v0.3.0...v0.3.1

v0.3.0

Full Changelog: https://github.com/asabirov/bcli/commits/v0.3.0