counterweight/personal_infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

signal-api: bump to 0.101 - Signal refused the old client

Browse source 
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>
This commit is contained in:
counterweight 2026-10-19 22:10:24 +02:00
parent a3d3f063f8
commit fba533ebb1
Signed by: counterweight
GPG key ID: 883EDBAA726BD96C
1 changed files with 13 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

19
ansible/roles/signal_api/defaults/main.yml
View file

@ -4,12 +4,19 @@
# Gatus does not speak Signal. It POSTs JSON to this service, which holds the # Gatus does not speak Signal. It POSTs JSON to this service, which holds the
# actual Signal identity and does the protocol work. # actual Signal identity and does the protocol work.
# Pinned by digest for the same reason as Gatus: a tag is mutable. # Pinned by DIGEST, with the release tag alongside for humans - same as Gatus.
# Upstream publishes no versioned tags worth pinning to, so this pins the # A tag is mutable; a digest is a content address, so `docker compose pull`
# DIGEST that `latest` resolved to when this was reviewed. `latest` is a moving # either fetches exactly this image or fails. Upstream publishes versioned
# target; a digest is a content address, and `docker compose pull` either # release tags (0.97 ... 0.101); the two values below must move together.
# fetches exactly this image or fails. #
signal_api_image_digest: "sha256:2399d449123cdad56c4d859277e3b9127e1a00c4d2ab4601c239882609286cf8" # THIS PIN EXPIRES. Signal's servers stop accepting signal-cli releases that
# fall a few months behind. 0.100 (signal-cli 0.14.5, 2026-06-11) was refused
# on 2026-10-18 - the phone reported "network error" and signal-cli logged
# "Link request error: Connection closed!", with the network itself fine. A
# stale pin fails exactly the same way for ALERTS: silently. Bump this at least
# every couple of months: https://github.com/bbernhard/signal-cli-rest-api/releases
signal_api_version: "0.101" # bundles signal-cli 0.14.8
signal_api_image_digest: "sha256:2cf09d66a86fdd210e42ee91662216364acc27da1163a8c44167a77ea3a6559a"
signal_api_image: "bbernhard/signal-cli-rest-api@{{ signal_api_image_digest }}" signal_api_image: "bbernhard/signal-cli-rest-api@{{ signal_api_image_digest }}"
signal_api_dir: /opt/signal-api signal_api_dir: /opt/signal-api