From 997a1c7f407cd0dfde65a676af822c305f1d4996 Mon Sep 17 00:00:00 2001 From: Krzysztof kuhy Rudnicki Date: Mon, 20 Jul 2026 08:59:00 +0200 Subject: [PATCH] MIGRATION.md: correct the pinned crdt_sync_dart tag to v0.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The doc claimed the migration pinned crdt_sync_dart-v0.3.0. It never did: phone_app/pubspec.yaml has said v0.2.0 since the migration commit itself (512fdd5), and pubspec.lock resolves it to 5be99ab. MIGRATION.md was written afterwards (21aa3bd) and got the number wrong, so the doc drifted, not the code — the build has always been v0.2.0. A v0.3.0 tag does exist upstream. Say so explicitly, and say that not using it is an untaken decision rather than a mismatch to reconcile, so the next reader doesn't "fix" the pubspec to match a doc that was wrong. Co-Authored-By: Claude Opus 4.8 (1M context) --- MIGRATION.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/MIGRATION.md b/MIGRATION.md index 2b8358b..e987b86 100644 --- a/MIGRATION.md +++ b/MIGRATION.md @@ -2,8 +2,10 @@ `phone_app`'s alarm sync was moved off a bespoke GitHub Gist onto the shared [`crdt_sync`](https://github.com/kuhyx/utils/tree/main/crdt_sync_dart) library -(pinned tag `crdt_sync_dart-v0.3.0`), matching how the other companion apps -sync. +(pinned tag `crdt_sync_dart-v0.2.0` — see `phone_app/pubspec.yaml`, which is +the authority; `pubspec.lock` resolves it to `5be99ab`), matching how the other +companion apps sync. A `crdt_sync_dart-v0.3.0` tag also exists upstream and is +*not* in use here — bumping to it is an untaken decision, not a drift to fix. ## What changed