@goodfish/jarvy 0.10.1 → 0.11.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,39 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to Jarvy. Versions follow [semantic versioning](https://semver.org/) as used before 1.0: a patch release only fixes bugs; a minor release adds features or upgrades the database.
|
|
4
4
|
|
|
5
|
+
## 0.11.1 — 2026-11-03
|
|
6
|
+
|
|
7
|
+
No database change: the schema stays v29.
|
|
8
|
+
|
|
9
|
+
### Fixed
|
|
10
|
+
|
|
11
|
+
- A Bot no longer fails its turn when, after its conversation is compacted, a batch carries a message in one of the threads it follows. The followed-thread list defined that thread and its channel a second time, differently from the batch's own definitions, and building the batch was refused: the turn failed before it reached the model, and the pending reminder failed every later turn too. The list now keeps the definition a batch already has, as the other notices do.
|
|
12
|
+
|
|
13
|
+
## 0.11.0 — 2026-11-02
|
|
14
|
+
|
|
15
|
+
No database change: the schema stays v29, and upgrading from 0.10.x needs nothing else. The live events stream (`/api/events`) and `GET /threads` changed shape; see **API** below.
|
|
16
|
+
|
|
17
|
+
### Added
|
|
18
|
+
|
|
19
|
+
- **Bots are reminded of the threads they follow.** After a Bot's conversation is compacted, its next batch lists the open threads it follows, the most recently active first (up to 15, with the total), each with its last reply and unread count, so work waiting in a thread isn't lost with the compaction. The reminder wakes no one and comes once. The `threads.follow` tool now tells a Bot to unfollow an open thread that no longer concerns it.
|
|
20
|
+
|
|
21
|
+
### Changed
|
|
22
|
+
|
|
23
|
+
- **「我关注的线程」 loads 30 threads at a time**, filtered and sorted on the server, so the page stays quick with hundreds of followed threads.
|
|
24
|
+
- **The thread pane loads 50 replies at a time**, and earlier ones as you scroll up; a long thread no longer freezes the page.
|
|
25
|
+
- **Live updates carry the change.** A new or updated message, or a change to a chat, arrives with its content and is put in place, instead of the page reading the chat list and the open conversation again. After a break of up to 10 minutes, a reconnecting page is sent what it missed rather than reloading. Three Bot messages in a DM went from about 950 KB of traffic to about 20 KB with a year of history.
|
|
26
|
+
- **A Bot's unread overview leaves finished threads out**: the unread list in its batches, the counts in `chats.list` and `messages.read unread=true` across chats skip threads marked done; asking for a thread by name still counts its unread. `messages.read unread=true` without a chat returns up to `limit` messages in all, with `hasMore`, instead of up to 30 from every chat.
|
|
27
|
+
- **Faster with a lot of history**: the followed-thread numbers are counted in one query (`GET /chats` 313 → 71 ms with a year of data), and starting a Bot's turn checks only its pending messages (0.7 s → 0.1 ms).
|
|
28
|
+
- **API**:
|
|
29
|
+
- `GET /threads` is paged (`filter`, `sort`, `cursor`, `limit`) and returns `{ threads, next }`; `GET /threads/:id` returns one row; `GET /chats` includes a `followed` summary.
|
|
30
|
+
- `/api/events` sends `message`, `message.updated`, `chat`, `chat.removed` and `bot`, each carrying what changed; the `inbox` event and the bare `chat {chatId}` event are gone. Events have ids: reconnect with `Last-Event-ID` (or `?after=`) to be sent what was missed, then `ready {resumed}`.
|
|
31
|
+
|
|
32
|
+
### Fixed
|
|
33
|
+
|
|
34
|
+
- The page reconnects its live connection when the server goes quiet: after 45 seconds without a heartbeat, 25 seconds when the page comes back to the foreground, and at once when the network returns. Bot status no longer stays stale after a dropped connection.
|
|
35
|
+
- Code blocks keep their horizontal scroll while the conversation updates.
|
|
36
|
+
- Deleting a scheduled task also removes its due notice if the Bot hadn't been told yet, and a notice with nothing left to say no longer fails the Bot's turn.
|
|
37
|
+
|
|
5
38
|
## 0.10.1 — 2026-10-29
|
|
6
39
|
|
|
7
40
|
No database change: upgrading from 0.10.0 needs nothing else.
|