Skip to content

docs(changelog): #333's entries are unreleased — 0.96.0 was cut before it merged #340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
leemour merged 1 commit into from
Oct 1, 2026
Merged

docs(changelog): #333's entries are unreleased — 0.96.0 was cut before it merged #340

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 7 additions & 11 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down
Loading