Repository navigation
v0.12.0
Fewer, parallel reads per refresh. Includes 0.11.1's security fix (redirects are never followed on token-bearing requests), so deploying 0.12.0 supersedes a pending 0.11.1 deploy. There is no change to authentication, the token file or the manifest's grants.
Changed
- One upstream
GET /tasksper refresh, down from two./tasks(unfiltered) and/headless-runsjoin one in-flight read. Only the read is shared, and nothing is served once it settles. Every mutation route, a Start's history write and the queue watcher invalidate it before responding, so a list requested after a mutation is always read after it. - The tab's three reads run in parallel, and after a button press the list and the task detail are re-read in parallel. Results apply last-started-wins.
- No second refresh after a button press. The watcher event for the tab's own write is skipped when a successful refresh already started after the change it reports. Changes made elsewhere still refresh live.
- A second click on the same task is ignored while its action is on the wire, Start included. Mutations are never sent in parallel or twice.
Measured (median of 7, against task-queue-mcp v0.13.0)
| 0.11.1 | 0.12.0 | |
|---|---|---|
| Tab load | 0.372 s, 3 upstream reads | 0.250 s, 2 upstream reads |
| Park + refresh | 0.382 s, 4 upstream reads | 0.268 s, 3 upstream reads |
Full notes: CHANGELOG.md. PR #15.