From 2a899ef9041c3c637380a91e532273a3581a19d1 Mon Sep 17 00:00:00 2001 From: SnapOtter Date: Mon, 6 Jul 2026 23:42:23 +0800 Subject: [PATCH] fix: remove duplicated 1.x migration callout in README (#456) Two PRs (#448 and #454) independently added the same "Coming from 1.x?" callout, and the merge landed both copies back to back. --- README.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/README.md b/README.md index 9fd1560e..e72baeaa 100644 --- a/README.md +++ b/README.md @@ -6,10 +6,6 @@ > [!IMPORTANT] > **Coming from 1.x?** Many of you have trusted SnapOtter since day one, and your feedback and suggestions shaped everything that followed. 2.0 is a big step, and we worked to make sure it doesn't break what you already depend on. Your accounts, saved files, settings, API keys, and pipelines carry over automatically on first boot, and your old database is never modified. We wrote a full [migration guide](./MIGRATING.md) so the move is safe and boring. Thank you for being here. - -> [!IMPORTANT] -> **Coming from 1.x?** Many of you have trusted SnapOtter since day one, and your feedback and suggestions shaped everything that followed. 2.0 is a big step, and we worked to make sure it doesn't break what you already depend on. Your accounts, saved files, settings, API keys, and pipelines carry over automatically on first boot, and your old database is never modified. We wrote a full [migration guide](./MIGRATING.md) so the move is safe and boring. Thank you for being here. -

Docker Hub GHCR