From 37955639c630e7cc8a476960dd5495e5ea0aa294 Mon Sep 17 00:00:00 2001 From: Jean-Pierre Martineau Date: Mon, 21 Sep 2026 04:01:28 -0400 Subject: [PATCH] MeshTerm 0.9.0 The first public release. The version goes to 0.9.0 and the changelog carries one entry, which the release job lifts verbatim as the release notes. [Unreleased] had refilled since the last fold with one change -- --mock keeping its invented mesh out of your real history. On a first release there is no previous behaviour for it to have changed from, so it is folded into the entry's existing --mock sentence, in that entry's voice, and [Unreleased] is empty again. Reading the notes as a newcomer would, three claims were not true, and each was checked against the running app rather than argued: - `meshterm map` is not a command. It was the first example a stranger would type, and it answers "No such command". The map is a picture, so it lives in the menu; the example is `meshterm info` now. - The Time Machine does not wind the map back. It is braille charts of recorded history over a day, a week, a month or all of it -- no map in it at all. - Only the PicoCalc gets the handheld layout. It is chosen solely by the device tree reading "Luckfox Lyra"; the uConsole has no detection and runs the desktop layout on its 1280x720 screen, which has the room for it. The manual's three sample outputs move from 0.3.7 to 0.9.0 with it, so the version a reader sees in docs/cli.md matches the one they downloaded. Co-Authored-By: Claude Opus 5 (1M context) --- CHANGELOG.md | 27 ++++++++++----------------- docs/cli.md | 6 +++--- meshterm/__init__.py | 2 +- 3 files changed, 14 insertions(+), 21 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index a7cfb80..07e7c08 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,16 +9,6 @@ one caveat SemVer makes for a leading zero: while the major version is still `0` ## [Unreleased] -### Changed - -- **`--mock` keeps its invented mesh out of your history.** The simulator is a fake radio, - not a fake MeshTerm: what it adverted was written to `meshterm.db` like anything a real - companion said, and its four invented contacts then turned up in the mesh walk, the - dashboard and the map of the mesh you actually run. A `--mock` run now records to - `meshterm-mock.db` beside it, created on first use. Naming a database with `--db` still - wins, and `$MESHTERM_HOME` is still the only thing that isolates a run whole — the - contact and channel caches, the outbox and the remembered devices are untouched by this. - ## [0.9.0] — 2026-09-22 **The first public release.** Everything in MeshTerm is new today, so instead of a list of @@ -34,7 +24,7 @@ what the mesh is doing. - **Run it two ways, and it behaves the same either way.** Type `meshterm` on its own and you get a full-screen menu you drive with the arrow keys. Type a command instead — - `meshterm contacts`, `meshterm map` — and it prints an answer and exits, which is what you + `meshterm contacts`, `meshterm info` — and it prints an answer and exits, which is what you want in a script. Add `--json` to any command and the answer comes back as data for another program to read. @@ -45,8 +35,9 @@ what the mesh is doing. what is happening now, but what was happening last Tuesday. - **You can see where everyone is.** There is a street map, drawn in the terminal, with the - radios on it. You can pan it, zoom it, and search it. There is also a Time Machine that - winds the map back so you can watch the mesh change over days. + radios on it. You can pan it, zoom it, and search it. There is also a Time Machine: charts of + everything you have ever overheard, so you can see when a radio usually talks and how + well you have heard it, over a day, a week, a month or all of it. - **You can talk to people.** Group channels and one-to-one messages, both live. If someone is out of range right now, the courier holds your message and delivers it when they come @@ -60,11 +51,13 @@ what the mesh is doing. - **It talks to your radio however your radio talks.** USB cable, Bluetooth, or over the network. It finds the ones it can find on its own and asks you to pick. If a connection drops it reconnects by itself. No radio yet? `meshterm --mock` runs the whole program - against a simulated mesh. + against a simulated mesh, and keeps that pretend mesh in a history of its own, so none + of it ever turns up beside your real one. -- **It runs on the small machines too.** There is a second layout built for handheld - consoles — the PicoCalc's 53-column screen and the uConsole — with its own fonts, colours - and on-screen key labels, not just the desktop screen squeezed. +- **It runs on the small machines too.** The PicoCalc gets a layout of its own, built + for its 53-column screen, with its own fonts, colours and on-screen key labels — not just + the desktop screen squeezed. The uConsole has room for the full desktop layout, and runs + that. - **It works with no internet.** Map tiles are kept on disk once fetched, and when there is no network at all the map falls back to a plain grid. Nothing about MeshTerm needs to diff --git a/docs/cli.md b/docs/cli.md index d1db5f3..8433ef2 100644 --- a/docs/cli.md +++ b/docs/cli.md @@ -1464,7 +1464,7 @@ each link; the scripted face prints the link alone. **`--json`:** ```json -{"page":"discord","title":"Join Discord","version":"0.3.7","text":"Join the Discord\n Questions, ideas, bug reports, and mesh talk.\n\n • https://discord.gg/AZwe5Uvb3S","links":["https://discord.gg/AZwe5Uvb3S"]} +{"page":"discord","title":"Join Discord","version":"0.9.0","text":"Join the Discord\n Questions, ideas, bug reports, and mesh talk.\n\n • https://discord.gg/AZwe5Uvb3S","links":["https://discord.gg/AZwe5Uvb3S"]} ``` | Field | Type | Meaning | @@ -1490,7 +1490,7 @@ resolved at boot and shown on no screen. ```console $ meshterm diagnostics -meshterm 0.3.7 +meshterm 0.9.0 install frozen os Windows 11 @@ -1566,7 +1566,7 @@ Under `--json`, the five fact blocks merge into one flat object and the two list a key of their own: ```json -{"meshterm":"0.3.7","install":"frozen","os":"Windows 11","…":"…","tables":[{"table":"observations","rows":418203}],"preferences":[{"preference":"log_level","value":"DEBUG"}]} +{"meshterm":"0.9.0","install":"frozen","os":"Windows 11","…":"…","tables":[{"table":"observations","rows":418203}],"preferences":[{"preference":"log_level","value":"DEBUG"}]} ``` **`--out PATH` writes it to a file instead of printing it**, and the answer becomes the diff --git a/meshterm/__init__.py b/meshterm/__init__.py index 709a318..cbde6ce 100644 --- a/meshterm/__init__.py +++ b/meshterm/__init__.py @@ -6,7 +6,7 @@ Supports USB, Bluetooth and TCP companion connection. For Windows, macOS and Lin from datetime import datetime -__version__ = "0.3.7" +__version__ = "0.9.0" __author__ = "Jean-Pierre Martineau" #: The year MeshTerm was first published; the copyright span starts here.