From 4e95cecf819c48f1c460271aee6724b2f7c96089 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 28 Jul 2026 21:47:38 +0300 Subject: [PATCH] Document why beeper-line is pinned to a commit hash Co-Authored-By: Claude Opus 5 (1M context) --- roles/custom/matrix-bridge-beeper-line/defaults/main.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/roles/custom/matrix-bridge-beeper-line/defaults/main.yml b/roles/custom/matrix-bridge-beeper-line/defaults/main.yml index 57a69cdbe..1a0bced50 100644 --- a/roles/custom/matrix-bridge-beeper-line/defaults/main.yml +++ b/roles/custom/matrix-bridge-beeper-line/defaults/main.yml @@ -13,6 +13,11 @@ matrix_bridge_beeper_line_container_image_self_build: false matrix_bridge_beeper_line_container_image_self_build_repo: "https://github.com/beeper/line.git" matrix_bridge_beeper_line_container_image_self_build_branch: "{{ 'main' if matrix_bridge_beeper_line_version == 'latest' else matrix_bridge_beeper_line_version }}" +# Unlike other components, this one is pinned to a commit hash and not to a version number. +# beeper-line's release tags are not maintained: the latest one (1.2.0) dates back to 2026-05-17 and lags behind the `main` branch by more than a hundred bugfix commits. +# This is because upstream releases by deploying the `main` branch from CI, not by tagging. +# Pinning to a tag would mean shipping a bridge which misses months' worth of fixes, so we pin to a commit from `main` instead. +# A side effect is that Renovate cannot track updates for this component, so its version needs to be bumped manually. matrix_bridge_beeper_line_version: 412eda7f028f0ee946d6fe584c64c7e97f27c7a7 # This image is maintained separately from the upstream project.