From eafca46baf47bf1b71f743b6c6ae2d42d56ced30 Mon Sep 17 00:00:00 2001 From: leemour Date: Thu, 1 Oct 2026 21:51:01 +0200 Subject: [PATCH] =?UTF-8?q?docs(changelog):=20#333's=20entries=20are=20unr?= =?UTF-8?q?eleased=20=E2=80=94=200.96.0=20was=20cut=20before=20it=20merged?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5.5 (1M context) --- CHANGELOG.md | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index c0431b50..582e0d51 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -24,6 +24,13 @@ Notable changes to `@leemour/cli-messaging`, one section per version, newest fir `commands --json` and an error from one copy was not an `instanceof` the other's class. What to change: depend on `@leemour/cli-core` yourself, at 0.13.0 or 0.14.x (tg-cli is on 0.14.0; max-cli, on 0.12.0, moves up), and drop the pnpm `overrides` entry for it once on this version. +- **The parity manifest marks `messages send --at-time`, `messages list --before-id|--before-time|--after-id| + --after-time` and `messages context --before-n|--after-n` as in both tools,** and drops the old `--at`, + `--before` and `--after` rows: max's main has moved (max-cli #294, #282). A max older than that fails + this manifest's parity check. +- **`store fetch --since|--max-pages` and `store export --since` are planned for max**, not max-only, so + max can move onto the shared `store` group (max-cli T6, 6c); they go once max's main has moved. + `store clear` is planned for max too: it comes with the store maintenance commands. ## 0.96.0 — 01.10.2026 @@ -51,16 +58,6 @@ Notable changes to `@leemour/cli-messaging`, one section per version, newest fir command, starts it again on that SQLite when a Linux distribution's Node brings one the store cannot use. On every other setup nothing changes. -### Changed — may break callers - -- **The parity manifest marks `messages send --at-time`, `messages list --before-id|--before-time|--after-id| - --after-time` and `messages context --before-n|--after-n` as in both tools,** and drops the old `--at`, - `--before` and `--after` rows: max's main has moved (max-cli #294, #282). A max older than that fails - this manifest's parity check. -- **`store fetch --since|--max-pages` and `store export --since` are planned for max**, not max-only, so - max can move onto the shared `store` group (max-cli T6, 6c); they go once max's main has moved. - `store clear` is planned for max too: it comes with the store maintenance commands. - ### Fixed - **`bot recipients`' help names `clear`**, the command that removes the list; it said `off`, which @@ -98,7 +95,6 @@ Notable changes to `@leemour/cli-messaging`, one section per version, newest fir events, so `bot auth show --trace` prints each request and the run record counts it. The third argument was `stop` alone; no CLI implements it yet. - ### Fixed - **`serve` and `watch` stopped by SIGTERM or Ctrl-C finish normally.** Telegram's library closes its