v1.1.2

1.1.2

• Fixed: syncing a mount could silently delete local-only changes. A pull
  overwrites/deletes local files to match the origin, and syncMount previously
  pulled whenever it was not pushing — so a read-only mount (or any mount whose
  local copy had diverged) would discard a newly created or edited file instead
  of preserving it. syncMount now only pushes when the mount is read-write and
  only the local side changed; any other divergent case raises
  ConflictDetectedException (via the new ConflictDetector.detectForPull)
  rather than destroying local work.
  • Added ConflictKind.localDivergence for a local copy that diverged from the
    baseline but cannot be published.

v1.1.1

1.1.1

• ManifestBuilder:

  • Updated default ignoredDirs to include .dart_tool directory.
  • Documentation updated to reflect the addition of .dart_tool to ignored directories.

• Dependency updates:

  • args: ^2.5.0 → ^2.7.0
  • crypto: ^3.0.3 → ^3.0.7
  • http: ^1.2.0 → ^1.6.0
  • path: ^1.9.0 → ^1.9.1
  • shelf: ^1.4.1 → ^1.4.2
  • lints: ^6.0.0 → ^6.1.0
  • test: ^1.25.6 → ^1.31.1

v1.1.0

1.1.0

• Added: per-file progress events during directory sync. DirectorySynchronizer.apply
  now emits a transferring ProgressEvent after each file is written or deleted (in
  both push and pull directions), carrying the path (message), cumulative bytes, and
  completed/total counts — enabling consumers to render live progress. Backward
  compatible: the start and done events are unchanged and progress stays optional.

v1.0.0

1.0.0

First stable release. Promotes the complete vertical slice — directory and git
providers, the hub + content HTTP servers, the OmnyClient SDK and the
omnydrive CLI — to a stable API, with content-addressed conflict detection
throughout.

• Domain model: drives, mounts, endpoints, sync refs, conflicts, capabilities.
• Providers: directory (HTTP-mirrored) and git (via the git CLI).
• Application layer: LocalDriveHub and LocalDriveEndpoint (publish, clone,
  sync) with content-addressed conflict detection.
• HTTP transport: hub server, endpoint content server, and matching clients
  (HttpDriveHub, HttpContentSource).
• Client SDK: OmnyClient and the package:omnydrive/omnydrive_client.dart
  surface.
• omnydrive CLI: serve, serve-content, login, publish, clone,
  sync, mounts, drives, with file-backed per-endpoint state.
• In-memory and file-backed persistence implementations.
• Runnable examples: core round-trip, conflict detection & resolution,
  read-only mirror, client SDK, and a git drive walkthrough.