From 0fc73ec760017903ee58fd821f1e26d274afbd00 Mon Sep 17 00:00:00 2001 From: MarekWo Date: Mon, 27 Jul 2026 12:11:55 +0200 Subject: [PATCH] chore(release): 2.2.0 Drop the -dev suffix and date the whatsnew section so release.sh can find its notes. Also make the build-string example in the whatsnew header read as an example, instead of naming one particular build that goes stale the moment it ships. Co-Authored-By: Claude Opus 5 --- VERSION | 2 +- docs/whatsnew.md | 8 +++++++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/VERSION b/VERSION index 97ade15..ccbccc3 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -2.2.0-dev +2.2.0 diff --git a/docs/whatsnew.md b/docs/whatsnew.md index f3c6bc6..a60623f 100644 --- a/docs/whatsnew.md +++ b/docs/whatsnew.md @@ -2,7 +2,7 @@ User-facing summary of changes since the last `main` release. Maintained on `dev` and finalized before each merge to `main`. -Releases are numbered `MAJOR.MINOR.PATCH` from **2.1.0** onward and tagged on GitHub — **MAJOR** when a deploy needs manual action from you, **MINOR** for new features, **PATCH** for fixes only. Sections before 2.1.0 are dated only; the project wasn't tagging releases yet. The exact build running on your server (`2026.07.26+95d96ec`) is still shown in the menu under the release number, for pinning down a specific deploy. +Releases are numbered `MAJOR.MINOR.PATCH` from **2.1.0** onward and tagged on GitHub — **MAJOR** when a deploy needs manual action from you, **MINOR** for new features, **PATCH** for fixes only. Sections before 2.1.0 are dated only; the project wasn't tagging releases yet. The exact build running on your server (a date and commit, like `2026.07.26+95d96ec`) is still shown in the menu under the release number, for pinning down a specific deploy. For deep technical notes, see [architecture.md](architecture.md). For the full git history, run `git log`. @@ -10,6 +10,12 @@ For deep technical notes, see [architecture.md](architecture.md). For the full g ## Unreleased +_Nothing yet since 2.2.0._ + +--- + +## 2.2.0 — 2026-07-27 + ### New features - **Quotes now use the `>` convention everyone else already uses.** Quoting a message used to wrap it in guillemets — `@[Daniel] »Hejka« Cześć!` — a shape mc-webui invented back when it couldn't send multi-line messages. It now puts the quote on its own line behind a `>` and drops the cursor underneath it, so a reply reads as a quote in the standard MeshCore app and every other client too, not just here: