From ed6069535acc4dd3cd1a38398c4b9767d23ac27a Mon Sep 17 00:00:00 2001 From: Strycher Date: Wed, 22 Jul 2026 01:39:41 -0400 Subject: [PATCH] chore(#367): cut 1.2.2+63 release (store consolidation notes + version) Bump pubspec to 1.2.2+63 and add the four release-gate docs (CHANGELOG section, GitHub release notes, Play what's-new, Discord post) for the #367/#370 desktop store-consolidation fix. Co-Authored-By: Claude Opus 4.8 --- CHANGELOG.md | 16 ++++++++++++++++ discord/1.2.2.md | 8 ++++++++ play/1.2.2.txt | 3 +++ pubspec.yaml | 2 +- release-notes/1.2.2.md | 15 +++++++++++++++ 5 files changed, 43 insertions(+), 1 deletion(-) create mode 100644 discord/1.2.2.md create mode 100644 play/1.2.2.txt create mode 100644 release-notes/1.2.2.md diff --git a/CHANGELOG.md b/CHANGELOG.md index fc57489..e3dc34d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,22 @@ All notable changes to Offband Meshcore. Pre-releases are tagged `-beta.N` / `-rc.N`. +## [1.2.2] - 2026-07-21 + +A follow-up to 1.2.1 that recovers desktop history left behind in other databases. + +### Fixed + +- Desktop (Windows/Linux): 1.2.1 pinned the database to one path but migrated only + a single prior store. A user who had run several differently-built copies could + have message history split across multiple databases, leaving the extras behind. + On launch, every discovered legacy store is now unioned into the pinned database + (messages by id, contacts by public key), so previously stranded history is + brought back in. Source databases are never deleted; a store that cannot be read + or is over a size guard is skipped and retried on a later launch, and a failed + run leaves every source intact. Android, web, and macOS were unaffected + (#367, #370). + ## [1.2.1] - 2026-07-21 A patch fixing a desktop data-location bug in 1.2.0. diff --git a/discord/1.2.2.md b/discord/1.2.2.md new file mode 100644 index 0000000..0f8abef --- /dev/null +++ b/discord/1.2.2.md @@ -0,0 +1,8 @@ +๐Ÿงต **Offband Meshcore 1.2.2** is up, a follow-up to 1.2.1. + +1.2.1 pinned your database to one place, but if you'd run several different builds on **Windows or Linux**, some history could still be sitting in other database files. 1.2.2 finds those on launch and merges them back into your main database, so history that still looked missing comes home. + +Your old databases are never touched, and if anything goes wrong it just retries next launch. Android and the web app aren't affected. + +๐Ÿ“ฅ **Download:** https://github.com/OffbandMesh/meshcore-client/releases/tag/v1.2.2 +๐ŸŒ **Web app:** https://offband.app diff --git a/play/1.2.2.txt b/play/1.2.2.txt new file mode 100644 index 0000000..8117c41 --- /dev/null +++ b/play/1.2.2.txt @@ -0,0 +1,3 @@ +Offband Meshcore 1.2.2 + +A small maintenance update that follows up 1.2.1. On desktop (Windows and Linux), any chat history left behind in older, separate databases is now found and merged back in automatically, with your original data left untouched. No changes are needed on Android. diff --git a/pubspec.yaml b/pubspec.yaml index 4cc004e..2b67d78 100644 --- a/pubspec.yaml +++ b/pubspec.yaml @@ -16,7 +16,7 @@ publish_to: 'none' # Remove this line if you wish to publish to pub.dev # https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html # In Windows, build-name is used as the major, minor, and patch parts # of the product and file versions while build-number is used as the build suffix. -version: 1.2.1+62 +version: 1.2.2+63 environment: sdk: ^3.9.2 diff --git a/release-notes/1.2.2.md b/release-notes/1.2.2.md new file mode 100644 index 0000000..54f3422 --- /dev/null +++ b/release-notes/1.2.2.md @@ -0,0 +1,15 @@ +## Offband Meshcore 1.2.2 + +A follow-up to 1.2.1 that brings back desktop history left behind in other databases. + +### Fixed + +- **Desktop (Windows/Linux): message history split across older databases is now + reunited.** 1.2.1 pinned the database to one location but only carried over a + single prior copy. If you had run several differently-built copies of the app, + some history could still be sitting in other database files. On launch, Offband + now finds those stores and merges them into the pinned database (messages by id, + contacts by public key), so history that looked missing comes back. Your old + databases are never deleted, and a run that hits a problem leaves every source + untouched and retries next launch. Android, web, and macOS were not affected + (#367, #370).