You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
New FeaturesKind: in v2.1.225,
New FeaturesSection of the release
What
In non-interactive mode a held peer message whose hold cause is a mode mismatch now gets a deadline, so a headless run no longer blocks indefinitely waiting for an approval that can never arrive.
Details
The expiry uses an unref'd timer, so it does not keep the process alive on its own.
On expiry the message is dropped and a cancelled receipt is issued to the sender.
The drop is logged with the reason that no approval surface exists.
Evidence
[cross-session-inbound] headless: held peer message expired (no approval surface) — dropped with an expired receipt
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
