spantaleev/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2026-07-30 02:44:33 +10:00
Code Issues Packages Projects Releases Wiki Activity

Document why beeper-line is pinned to a commit hash

Browse Source 
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Slavi Pantaleev
2026-07-28 21:47:38 +03:00
parent 641b9e989d
commit 4e95cecf81
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
roles/custom/matrix-bridge-beeper-line/defaults/main.yml
+5
View File
@@ -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.