Files
helm-charts/rss-bridge/Chart.yaml
T
jklein bcbcc2c62f rss-bridge: app update 2025-06-03 -> 2025-08-05
One step: 2025-08-05 is the immediate successor release, no publication
in between (verified against the project's release list). Tag present on
Docker Hub for amd64 and arm64.

Patch bump, because the changelog review found nothing that touches the
values surface or the chart's behaviour. Checked against the shipped
source of both images rather than against the release notes:

- whitelist.txt format: lib/Configuration.php is byte-identical apart
  from its VERSION constant, so the parsing the chart relies on (trim,
  split on newline, drop empty entries, "*" wildcard) is unchanged.
- the five production bridges: all present, none renamed. Youtube,
  TheHackerNews, ARDMediathek and Reddit are byte-identical; Heise has a
  content-level change only (paywalled heise+ items now carry an
  archive.is link, two more CSS selectors stripped). The three bridges
  removed upstream - Askfm, DansTonChat, FirstLookMediaTech - are none
  of ours.
- RSSBRIDGE_* environment mapping: same file, therefore unchanged.
- write paths: re-derived empirically rather than inferred, because the
  opcache lock file in /tmp appears in no filesystem diff. The new image
  needs exactly the same five, and a control run without /tmp still dies
  with "Unable to create lock file: Read-only file system".
- health endpoint: actions/ is identical, /?action=health intact.
- PHP 8.2.28 -> 8.2.29, nginx and Debian unchanged, so the
  /run/php/php8.2-fpm.sock path the chart mounts still applies. Measured
  fresh-start peak under five concurrent feed fetches: 64.5 MiB on the
  new image against 71.1 MiB on the old one under an identical
  procedure. Requests and limits stay as they are.

The memory comments in values.yaml are refreshed to the image the chart
now ships, and the older 119 MiB figure is labelled as what it was - a
warm container, not a fresh start.

We stay on the dated release tag. The newest release is itself over
twelve months old and the project now pushes latest and commit-based
sha-* tags continuously, but a sha-* tag is not more released than the
release, only newer, and latest is rolling - both conflict with the
repo's convention of reproducible pinned tags.

Fixes #135
2026-08-23 23:59:47 +02:00

13 lines
288 B
YAML

apiVersion: v2
name: rss-bridge
description: A Helm chart to deploy RSS-Bridge on Kubernetes
icon: https://raw.githubusercontent.com/RSS-Bridge/rss-bridge/master/static/logo_300px.png
type: application
version: 1.0.1+up2025.08.05
appVersion: "2025-08-05"
maintainers:
- name: jklein