From cd1050d116def73dfabaab887ca76611c4c5f16c Mon Sep 17 00:00:00 2001 From: diffwireauto <330573775+diffwireauto@users.noreply.github.com> Date: Mon, 26 Oct 2026 21:10:24 -0400 Subject: [PATCH] chore(#1006): cut 1.7.0+68 (production, staged rollout) Bump pubspec to 1.7.0+68 and add the four release-gate docs (CHANGELOG [1.7.0], GitHub release notes, Play what's-new at 403/500, Discord post). Content: per-message storage with the one-way schema 1 to 2 upgrade, radio-profile isolation, sync-is-truth contacts, custom contact names, region scoping, the Settings restructure, CLI for stock 1.18 companions, and the bounded BLE reconnect. The release notes, Play text, and Discord post carry the #953 disclosure: earlier versions cannot open the converted database. Firmware caveats stated per feature: regions need companion 1.16+ or current Offband firmware (verified in offband-v1.5.0-beta7 and v1.6.0-beta1); CLI needs stock 1.18; the 0xC5 badge settings stay hidden until Offband firmware ships them (f3d30a88 is in no firmware tag yet). Build task under release tracker #1005. Part of epic #312. Co-Authored-By: Claude Opus 5.5 --- CHANGELOG.md | 87 ++++++++++++++++++++++++++++++++++ discord/1.7.0.md | 25 ++++++++++ play/1.7.0.txt | 3 ++ pubspec.yaml | 2 +- release-notes/1.7.0.md | 105 +++++++++++++++++++++++++++++++++++++++++ 5 files changed, 221 insertions(+), 1 deletion(-) create mode 100644 discord/1.7.0.md create mode 100644 play/1.7.0.txt create mode 100644 release-notes/1.7.0.md diff --git a/CHANGELOG.md b/CHANGELOG.md index 02f15b87..d0a08899 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,93 @@ All notable changes to Offband Meshcore. Pre-releases are tagged `-beta.N` / `-rc.N`. +## [1.7.0] - 2026-10-26 + +Production successor to 1.6.0. A foundations release: per-message storage with a +one-way schema upgrade, radio-profile isolation, sync-is-truth contacts, custom contact +names, region scoping, a Settings restructure, and CLI for stock 1.18 companions. + +### Storage (one-way upgrade, schema 1 to 2) + +- History stored **one drift row per message** with a verified blob-to-rows + migration; save cost no longer grows with history (#917, #920). +- Blob read-modify-write, DM save merges, and both delete paths moved **off the UI + isolate** (#919). +- A newer schema is **refused loudly** instead of rewriting the version; the migration + gate asserts a superset, so keys with extra rows no longer stay stuck (#943, #952). +- **Stale blob reclamation**: per-key migration timestamps, an automatic sweep after + 30 days, a durable audit of what it deleted, and **Clear Stale History Now** in App + Settings > Storage that reports refusals (#962, #965, #966). +- Earlier versions cannot open a schema-2 database; disclosed in the release texts + (#953). + +### Radio-profile isolation (#853) + +- Scoping inventory with a verdict gate, and repros of the remaining bleeds (#936). +- Path history and delivery observations per radio; dead `pending_messages` API + removed (#937). +- Discovered contacts per radio (#754); a blank radio is no longer pre-blocked from + another radio's list (#471); Blocked pane says "No radio connected" (#938). +- Storage scope keys cleared on an unexpected disconnect, closing the stale-read window + (#939); full isolation matrix across a radio switch and a restart (#940). +- Channel notify modes scoped per radio, index fallback removed, set-and-back resets + (#839, #848). + +### Contacts + +- **Sync is truth**: live adverts (0x8A, 0x88) feed discovery only; the persisted list + comes from the radio's contact sync, with a debounced incremental reconcile when an + advert matches the radio's auto-add policy (#838, #842, #850). +- **Custom Name**: `customName` over `receivedName`, kept off the wire and out of + exports and contact shares, scoped per radio (#750). + +### Region scoping (#812) + +- Region model and name-derived transport key; flood-scope frames and anon-regions + discovery, gated on `FIRMWARE_VER_CODE >= 13` (#813, #820, #821, #822). +- Discover Regions service and screen (#814, #825, #826); per-channel region-scope + store, Set Region Scope action, and per-send scoping (#815, #829, #830, #831). +- Hardware fixes: searchable, path-aware repeater picker; corrected discovery request + format, multi-hop reply path, firmware-estimate timeout, one auto-retry (#830, #836). + +### Settings and badge parity (#975) + +- Location is a top-level category and the only home for GPS (#977); Button actions in + Node Settings, Buzzer and tones in Message Settings (#978). +- Over 0xC5, capability-gated: GPS mode and power-save interval (#969), event tones + (#986), custom tunes with RTTTL order check and Fix order (#970), screen settings + (#971, #987), channel tune codec (#981). Requires Offband firmware not yet released. +- Config import/export, GPX exports, and "Sync queued messages now" moved to Actions; + Debug reordered (#902). + +### CLI (stock 1.18 companions) + +- Population classifier and capability-gate rework (#866, #875, #876, #877, #878, + #880); stock 1.18.0 classified by frame shape, not version suffix (#946). +- Companion CLI codec (frame 66/29), local CLI service, and Device CLI console + (#868, #881, #882, #883, #884). +- Remote CLI to companions: contact permission flag 0x10, role-based TXT type, command + service generalized to companions, inbound type 3, CLI kept out of chat, console + offered only on a 1.18 radio (#870, #887, #888, #889, #890, #891, #999). + +### Bluetooth and stability + +- Bounded, interruptible auto-reconnect: 5 attempts or 3 minutes, Stop ends it, a user + connect wins; a connect waits for a disconnect still in progress (#996, #997). +- Windows: use-after-free crash on app close fixed (#989). +- ANR and exit-record capture via ApplicationExitInfo, shipped with the exported log + (Android 11+) (#906, #910, #931). + +### Fixes + +- Channel hop counts decoded from the packed path-len byte, so 2- and 3-byte path + hashes render the right hop count (#985). + +### CI + +- CI no longer reports a pass without running; Linux pinned to ubuntu-24.04 (#927, + #929); docs-only changes short-circuit the required checks (#904, #905). + ## [1.6.0] - 2026-10-05 First stable release of the 1.5.0 line and the production successor to 1.4.0. A large diff --git a/discord/1.7.0.md b/discord/1.7.0.md new file mode 100644 index 00000000..6f25ee1a --- /dev/null +++ b/discord/1.7.0.md @@ -0,0 +1,25 @@ +πŸš€ **Offband Meshcore 1.7.0 is out.** A foundations release: faster storage, every radio keeps its own data, and a contact list that matches your radio. Over 100 changes since 1.6.0. + +⚠️ **Read this before updating: it's a one-way upgrade.** On first launch, 1.7.0 converts your message history to a new database format. After that, **older versions of the app can't open it**, so there's no going back to 1.6.0. Your messages carry over. The old copy is kept 30 days and then cleared automatically, so the database is bigger for a while. Want the space back now? **App Settings > Storage > Clear Stale History Now** (it asks first and never touches your messages). + +πŸ’Ύ **Storage that keeps up.** One row per message instead of one giant blob per conversation, so a new message costs the same at 50,000 messages of history as at 50, and the heavy lifting is off the UI thread. + +πŸ“» **Every radio keeps its own data.** Discovered nodes, blocked contacts, channel notification modes, path history, and delivery records all belong to the radio they came from. A brand-new radio no longer shows up pre-blocked, and switching radios no longer flashes the last radio's history. + +πŸ‘₯ **Contacts that match your radio.** No more phantom contacts piling up from adverts your radio rejected; a contact your radio actually stores still shows up on its own. And **custom names**: rename any contact, keep seeing what the node calls itself underneath, and your label never goes over the air or into exports. + +πŸ—ΊοΈ **Region scoping.** Discover a repeater's regions and scope a channel to one, so its messages flood only there. Needs MeshCore companion 1.16+ or current Offband firmware. + +βš™οΈ **Settings, reorganized.** Location gets its own category (and is the one home for GPS), Buzzer and tones moves to Message Settings, and import/export plus GPX live under Actions. Badge tones, custom tunes, screen settings, and GPS power save are built in and will appear once the matching Offband firmware ships. + +πŸ–₯️ **CLI for stock 1.18 companions.** A Device CLI console for your radio, remote CLI to another companion from the chat menu, and a per-contact Remote CLI permission toggle. CLI stays out of your chat. + +πŸ“Ά **Steadier Bluetooth.** Auto-reconnect now gives up after 5 tries or 3 minutes, **Stop** ends it right away, and a connect you start always wins. Plus a fix for a race that could leave the composer unusable, and a Windows crash on close. + +πŸ”§ **Fixes.** Messages with 2- or 3-byte path hashes show the right hop count (no more 13 hops reading as 39). + +**πŸ“₯ Get it on Google Play:** search **Offband MeshCore**, or https://play.google.com/store/apps/details?id=app.offband.meshcore (rolling out in stages, so it may take a few days to reach you) +πŸ’» **Desktop (Windows / Linux) and Android APK:** https://github.com/OffbandMesh/meshcore-client/releases/tag/v1.7.0 +🌐 **Or run it in your browser:** https://offband.app + +πŸ’š Thanks as always to the **OKIMesh community** (https://okimesh.org/). Offband is open source and always will be; if you'd like to help keep it going: https://offband.org/donate diff --git a/play/1.7.0.txt b/play/1.7.0.txt new file mode 100644 index 00000000..7dbcfe1d --- /dev/null +++ b/play/1.7.0.txt @@ -0,0 +1,3 @@ +Offband Meshcore 1.7.0 + +Message history moves to a faster storage format on first launch. After updating, earlier versions of the app cannot open it. Each radio now keeps its own contacts, blocks, and notification settings. The contact list follows your radio, with no phantom contacts. Give any contact a custom name. Region scoping for channels, a tidier Settings, and a steadier Bluetooth reconnect. diff --git a/pubspec.yaml b/pubspec.yaml index c34e5ee2..61ec2e79 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.6.0+67 +version: 1.7.0+68 environment: sdk: ^3.9.2 diff --git a/release-notes/1.7.0.md b/release-notes/1.7.0.md new file mode 100644 index 00000000..6fc88e19 --- /dev/null +++ b/release-notes/1.7.0.md @@ -0,0 +1,105 @@ +## Offband Meshcore 1.7.0 + +A foundations release. Message history moves to a new storage format that stays fast no +matter how much of it you have, every radio you connect now keeps its own data, and the +contact list follows what your radio actually holds. On top of that: custom contact +names, region scoping for channels, a reorganized Settings, a CLI console for stock +MeshCore 1.18 companions, and a steadier Bluetooth reconnect. Over 100 changes since +1.6.0. + +### Please read before updating: a one-way storage upgrade + +The first time 1.7.0 starts, it converts your message history to a new database format. +**After that, going back to an earlier version of the app is not possible**: older +versions cannot open the converted database. Your messages carry over; the conversion +checks every conversation and keeps the original data for any it cannot verify. + +The old copy of your history is kept for 30 days and then cleared automatically. Until +then the database is larger than before, because it briefly holds your history twice. +To reclaim that space now, use **App Settings > Storage > Clear Stale History Now**. It +asks first, shows what will be cleared, and never touches your messages. Anything it +cannot verify, it keeps and tells you so (#917, #919, #920, #943, #952, #962, #965, #966). + +### Message storage that keeps up + +- History is stored **one row per message** instead of one large block per + conversation, so receiving a message costs the same at 50,000 messages of history as + at 50 (#920). +- Saving, merging, and deleting history now run **off the UI thread**, so a long + channel no longer stalls the screen (#919). + +### Every radio keeps its own data + +If you use more than one radio, switching between them no longer mixes their data: + +- **Discovered nodes** belong to the radio that heard them (#754). +- **Blocked contacts** belong to the radio that holds them, and a brand-new radio no + longer comes up with another radio's blocks (#471). With no radio connected, the + Blocked pane says so instead of looking empty (#938). +- **Channel notification modes** are set per radio and can be reset properly (#839). +- **Path history and delivery records** are kept per radio (#937). +- After a dropped connection, connecting a different radio no longer briefly shows the + previous radio's history (#939). Isolation is checked across radio switches and app + restarts (#940). + +### Contacts that match your radio + +- The contact list now comes from your radio's own contact sync. Overheard adverts the + radio rejected (past its hop limit or capacity) no longer pile up as phantom + contacts, and a contact the radio does store still appears on its own, with no + manual sync needed (#838). +- **Custom names**: give any contact a name of your own. Adverts keep updating what the + node calls itself underneath without moving your label, and where the two differ you + can see both. Your label is never sent over the air or included in exports or + contact shares. Custom names belong to the radio you set them on (#750). + +### Region scoping + +- **Discover the regions** a repeater knows, then **set a channel's region scope** so + its messages flood only within that region. The repeater picker is searchable and + lists the repeaters you can actually reach (#812, #830, #836). +- Requires MeshCore companion firmware 1.16 or newer, or current Offband firmware. On + older firmware the option stays hidden. + +### Settings, reorganized + +- **Location** is its own Settings category and the one place for GPS (#977). +- **Button actions** stay in Node Settings, and **Buzzer and tones** moves to Message + Settings, since some boards have a buzzer and no buttons (#978). +- Config import and export, GPX exports, and "Sync queued messages now" moved to + **Actions**, and the Debug section is reordered (#902). +- Event tones, custom tune editing, screen settings, and a GPS Off / On / Power save + control are built in, and appear only on a radio whose Offband firmware supports + them. That firmware is not released yet, so for now these stay hidden (#969, #970, + #971, #981, #986, #987). + +### CLI for stock MeshCore 1.18 companions + +- A **Device CLI console** for the connected radio, at the top of the Debug section, + with per-reply timing and secret replies masked (#868). +- **Remote CLI** to another companion over the mesh, from the chat menu's CLI console + action, plus a per-contact **Remote CLI** permission toggle that controls who may run + CLI on your radio. CLI traffic stays in the console and out of your chat (#870). +- Both need a stock MeshCore 1.18 companion; on other firmware they stay hidden. + +### Bluetooth and stability + +- **Automatic reconnect is bounded**: it stops after 5 attempts or 3 minutes, + whichever comes first, **Stop** ends it immediately, and a connection you start + yourself always takes over (#997). +- A connection started while a disconnect was still finishing no longer leaves the + status stuck and the composer unusable (#997). +- Windows: fixed a crash when closing the app (#989). + +### Fixes + +- Messages with 2- or 3-byte path hashes show the right hop count (a 13-hop message + no longer reads as 39 hops), and the Packet Path screen agrees with the chat (#985). +- The Device CLI console now appears on stock MeshCore 1.18.0 radios whose version + string carries a build suffix (#946). + +### For troubleshooting + +- On Android 11 and newer, the exported debug log now includes the system's own record + of why the app last stopped, including any "app not responding" trace, so a report + can explain a freeze without anyone digging (#906).