Skip to content

v2.0.0

Choose a tag to compare

@github-actions github-actions released this 26 Sep 20:20
· 11 commits to main since this release

2.0.0 — the tincan connector requires tincan 2.0.0 or newer, and reports a deduplicated delivery honestly.

Two breaking changes, both in the tincan notification route.

A route configured against tincan 1.10.1 now refuses to start until tincan is upgraded. The startup probe asks tincan send --help and reads the exit code, which tincan 2.0.0 documents as its capability check; every older build exits non-zero. It previously matched the string 'unrecognised argument' on stderr, because 1.9.2 and 1.10.1 both exited non-zero from a bare send and only the wording told them apart — that wording was tincan's usage prose rather than an interface, so a reword would have silently turned the probe into one that accepts a tincan that cannot deliver.

The meaning of a recorded delivery outcome has changed. duplicate_send is now reported as delivered rather than delivery_unknown. tincan 2.0.0 added a duplicate_peer_moved refusal for the retry whose target name has since moved to a different session, so duplicate_send now means the peer being addressed really does hold the message — the same claim accepted makes. Only the moved case stays delivery_unknown, which restores the ordinary retry path.

These are one change, not two: reporting a duplicate as delivered is only true where the other refusal exists to carry the moved case, so refusing every older tincan is what keeps it honest. 1.10.1 has send and delivers, and is refused for lacking the refusal rather than the subcommand.

Note that tincan's own 2.0.0 is not an API break — that major covers their clean-history republish and the npm provenance discontinuity that came with it.

Also in this release: docs/decisions.md D6 is revisited against an instrumented corpus now that activity_resolution exists, keeping the decision that no_progress ships with no default but narrowing the reason to a missing measurement rather than a missing principle; scripts/replay-activity.mjs keeps that replay so it need not be written from scratch again; and docs/troubleshooting.md gains an entry pointing a stuck session at no_progress.