v0.2.4

Fix infinite loop in pagination by using GROUP BY with MAX(updated_at) instead of selectDistinct

v0.2.3

fix: use last change timestamp as pagination cursor

Previously, serverTimestamp was set to new Date().toISOString() which returned the current server time. This caused pagination to fail because the next page would use a timestamp in the future as cursor, returning 0 changes.

Now serverTimestamp correctly returns the updatedAt of the last returned change, ensuring pagination continues from the correct position.

v0.2.1 - Migration Fix

Bug Fixes

• fix: Remove duplicate column operations in migration 0004

Migration 0003 already handles the column rename (nonce -> vault_key_nonce) and adding the new columns. Migration 0004 was incorrectly trying to do the same operations again, causing failures on fresh database setups.

v0.2.0

What's Changed

Breaking Changes

• Changed /sync/pull endpoint from POST to GET
• Removed deprecated operation field from sync schema and API responses

Features

• Added deviceId field to sync changes for better device tracking
• Column-level CRDT sync with server-side deduplication
• DELETE endpoint for vault deletion

Improvements

• Cleaned up migration files (removed redundant migration 0006)
• Updated sync response format to align with new schema

Full Changelog: v0.1.0...v0.2.0