Files
truecharts/charts/stable/dispatcharr
TrueCharts Bot 1fda2be3c4 fix(dispatcharr): update image docker.io/dispatcharr/dispatcharr 0.27.1 → 0.27.2 (#49705)
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

<details>
<summary>Dispatcharr/Dispatcharr
(docker.io/dispatcharr/dispatcharr)</summary>

###
[`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**.

</details>

---

### 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.

---

- [ ] <!-- rebase-check -->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).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xMzAuMSIsInVwZGF0ZWRJblZlciI6IjQzLjEzMC4xIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbImFwcC9kaXNwYXRjaGFyciIsImF1dG9tZXJnZSIsInJlbm92YXRlL2NvbnRhaW5lciIsInR5cGUvcGF0Y2giXX0=-->
2026-06-30 21:15:26 +02:00
..

title
title
README

General Info

For more information about this Chart, please check the docs on the TrueCharts website

This chart is not maintained by the upstream project and any issues with the chart should be raised here

Installation

Helm-Chart installation

To install TrueCharts Helm charts using Helm, you can use our OCI Repository.

helm install mychart oci://oci.trueforge.org/truecharts/dispatcharr

For more information on how to install TrueCharts Helm charts, checkout the instructions on the website

Chart Specific Guides and information

All our charts have dedicated documentation pages. The documentation for this chart can be found here: https://truecharts.org/charts/stable/dispatcharr

Configuration Options

To view the chart specific options, please view Values.yaml included in the chart. The most recent version of which, is available here: https://github.com/trueforge-org/truecharts/blob/master/charts/stable/dispatcharr/values.yaml

All our Charts use a shared "common" library chart that contains most of the templating and options. For the complete overview of all available options, please checkout the documentation for them on the common docs on our website

For information about the common chart and all defaults included with it, please review its values.yaml file available here: https://github.com/trueforge-org/truecharts/blob/master/charts/library/common/values.yaml

Support


Sponsor TrueCharts

TrueCharts can only exist due to the incredible effort of our staff. Please consider making a donation or contributing back to the project any way you can!

All Rights Reserved - The TrueCharts Project