counterweight fba533ebb1 signal-api: bump to 0.101 - Signal refused the old client ... Relinking after the rebuild failed: the phone said "network error" and signal-cli logged "Link request error: Connection closed!", with the network itself fine (TLS to chat.signal.org completed). The pinned 0.100 bundled signal-cli 0.14.5 from June; Signal stops accepting clients that fall a few months behind. 0.101 (signal-cli 0.14.8) linked first time. A stale pin fails the same way for alerts - silently - so the pin now carries signal_api_version beside the digest and a note to bump it every couple of months. The old comment saying upstream publishes no versioned tags was wrong. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>		2026-10-19 22:10:24 +02:00
..
group_vars	ntfy-emergency-app: remove it	2026-10-19 22:10:22 +02:00
host_vars	monero: check every five minutes again	2026-10-19 22:10:24 +02:00
infra	gatus: service checks tolerate one failed run	2026-10-19 22:10:24 +02:00
playbooks	jar-lid-archive: a staging deployment on its own box	2026-10-03 23:56:30 +02:00
roles	signal-api: bump to 0.101 - Signal refused the old client	2026-10-19 22:10:24 +02:00
services	playbooks: stop re-runs overwriting live config	2026-10-19 22:10:23 +02:00
ansible.cfg	now using password	2026-09-11 17:59:41 +02:00
inventory.ini	rebuild: fold monitoring into spacey and prd-arbret into vipy	2026-10-19 22:10:22 +02:00
requirements.yml	uptime-kuma: annotate config and drop the unused collection	2026-09-11 22:43:56 +02:00
site.yml	ntfy-emergency-app: remove it	2026-10-19 22:10:22 +02:00