From 1fda2be3c44c8a4be7b92f813de24a3c22dca081 Mon Sep 17 00:00:00 2001 From: TrueCharts Bot Date: Tue, 30 Jun 2026 21:15:26 +0200 Subject: [PATCH] =?UTF-8?q?fix(dispatcharr):=20update=20image=20docker.io/?= =?UTF-8?q?dispatcharr/dispatcharr=200.27.1=20=E2=86=92=200.27.2=20(#49705?= =?UTF-8?q?)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This PR contains the following updates: | Package | Update | Change | |---|---|---| | [docker.io/dispatcharr/dispatcharr](https://redirect.github.com/Dispatcharr/Dispatcharr) | patch | `f5cbc82` → `f2b5ea3` | --- > [!WARNING] > Some dependencies could not be looked up. Check the [Dependency Dashboard](../issues/18710) for more information. Add the preset `:preserveSemverRanges` to your config if you don't want to pin your dependencies. --- ### Release Notes
Dispatcharr/Dispatcharr (docker.io/dispatcharr/dispatcharr) ### [`v0.27.2`](https://redirect.github.com/Dispatcharr/Dispatcharr/blob/HEAD/CHANGELOG.md#0272---2026-06-30) [Compare Source](https://redirect.github.com/Dispatcharr/Dispatcharr/compare/v0.27.1...v0.27.2) ##### Added - **New proxy setting: Client Connect Grace Period (`channel_client_wait_period`, default 5s).** Adds a dedicated timeout for channels that have filled their buffer but still have no viewers (`waiting_for_clients`). Previously that window reused `channel_shutdown_delay` (default 0s), so those channels were torn down almost immediately. ##### Changed - **Proxy grace-period settings are now split into three distinct timeouts.** The cleanup watchdog already applied `channel_init_grace_period` while a channel was still connecting (buffer not ready) and reused `channel_shutdown_delay` once `connection_ready_time` was set, including for `waiting_for_clients` with zero viewers. With the default `channel_shutdown_delay` of 0s, a buffered channel waiting for its first viewer was stopped almost immediately; raising shutdown delay was the only workaround, but that also delayed teardown after real disconnects. Behaviour is now: - **`channel_init_grace_period` (default 60s, max 300s):** how long the proxy may spend connecting and cycling failover streams before giving up on startup. - **`channel_client_wait_period` (default 5s):** how long a ready channel with no viewers stays up waiting for the first client (the original grace-period use case). - **`channel_shutdown_delay` (default 0s):** delay after the last client disconnects only; no longer applies when the buffer is ready but no viewer has connected yet. - **Migration 0026 bumps `channel_init_grace_period` to 60s when the stored value is below 60.** Existing installs on the old 5s default (or any custom value under 60) are raised automatically. Values already at 60s or higher are unchanged. If you previously raised `channel_shutdown_delay` to keep buffered channels alive with no viewers, set `channel_client_wait_period` instead (Settings → Proxy → Advanced). - **Proxy settings UI: less-used options moved under Advanced.** Settings → Proxy now shows the day-to-day tuning fields by default (`buffering_timeout`, `buffering_speed`, `channel_shutdown_delay`, `new_client_behind_seconds`). **Buffer Chunk TTL**, **Channel Initialization Timeout**, and **Client Connect Grace Period** are tucked under **Show Advanced Settings**.
--- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). --- charts/stable/dispatcharr/Chart.yaml | 4 ++-- charts/stable/dispatcharr/values.yaml | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/charts/stable/dispatcharr/Chart.yaml b/charts/stable/dispatcharr/Chart.yaml index 817b628f2f1..e2ef1a6388e 100644 --- a/charts/stable/dispatcharr/Chart.yaml +++ b/charts/stable/dispatcharr/Chart.yaml @@ -9,7 +9,7 @@ annotations: trueforge.org/min_helm_version: "3.14" trueforge.org/train: stable apiVersion: v2 -appVersion: 0.27.1 +appVersion: 0.27.2 dependencies: - name: common version: 29.6.0 @@ -37,5 +37,5 @@ sources: - https://github.com/trueforge-org/truecharts/tree/master/charts/stable/dispatcharr - https://hub.docker.com/r/dispatcharr/dispatcharr type: application -version: 2.12.0 +version: 2.12.1 diff --git a/charts/stable/dispatcharr/values.yaml b/charts/stable/dispatcharr/values.yaml index 10e9ca552e1..ad5c8bd84ca 100644 --- a/charts/stable/dispatcharr/values.yaml +++ b/charts/stable/dispatcharr/values.yaml @@ -2,7 +2,7 @@ image: pullPolicy: IfNotPresent repository: docker.io/dispatcharr/dispatcharr - tag: 0.27.1@sha256:f5cbc82f4cfdb0f5ace2a4d09a5e115aa52cd92218fb88e79b103fe32aceb315 + tag: 0.27.2@sha256:f2b5ea3128b0513feb07efee7539ad546f3ba3a9095f19936f446f75b8baa894 securityContext: container: readOnlyRootFilesystem: false