chore(container): update image ghcr.io/dispatcharr/dispatcharr ( 0.25.0 → 0.25.1 ) - #1780
Merged
Merged
Conversation
--- kubernetes/apps/arr/dispatcharr/app Kustomization: arr/dispatcharr HelmRelease: arr/dispatcharr
+++ kubernetes/apps/arr/dispatcharr/app Kustomization: arr/dispatcharr HelmRelease: arr/dispatcharr
@@ -39,13 +39,13 @@
DISPATCHARR_LOG_LEVEL: info
REDIS_HOST: localhost
TZ: null
image:
pullPolicy: IfNotPresent
repository: ghcr.io/dispatcharr/dispatcharr
- tag: 0.25.0
+ tag: 0.25.1
probes:
liveness:
enabled: false
resources:
limits:
memory: 2Gi |
--- HelmRelease: arr/dispatcharr Deployment: arr/dispatcharr
+++ HelmRelease: arr/dispatcharr Deployment: arr/dispatcharr
@@ -42,13 +42,13 @@
- name: DISPATCHARR_LOG_LEVEL
value: info
- name: REDIS_HOST
value: localhost
- name: TZ
value: null
- image: ghcr.io/dispatcharr/dispatcharr:0.25.0
+ image: ghcr.io/dispatcharr/dispatcharr:0.25.1
imagePullPolicy: IfNotPresent
name: app
resources:
limits:
memory: 2Gi
requests: |
renovate
Bot
force-pushed
the
renovate/ghcr.io-dispatcharr-dispatcharr-0.x
branch
from
May 28, 2026 22:26
adddf8b to
43d833f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.25.0→0.25.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
Dispatcharr/Dispatcharr (ghcr.io/dispatcharr/dispatcharr)
v0.25.1Compare Source
Fixed
SynchronousOnlyOperationand permanent loading state in series rules save._evaluate_series_rules_lockedandreschedule_upcoming_recordings_for_offset_change_implcalledasync_to_sync(channel_layer.group_send)directly from WSGI views. In a uWSGI/gevent worker this has two effects: (1) it sets Python 3.10+'s C-level OS-thread-local running-loop flag, causing Django's@async_unsafeguard to raiseSynchronousOnlyOperationon any ORM call made by another greenlet on the same thread; (2) the asyncio event loop it creates cannot make progress because the gevent hub is blocked waiting for the request greenlet to complete, so the request hangs and the frontend spinner never clears. Both functions now usesend_websocket_update- the same gevent-aware helper used elsewhere - which takes a direct Redis path (no asyncio) in gevent workers. (Fixes #1260)auto_created=Truebut getauto_created_by=NULLwhen the originating M3U account is deleted (on_delete=SET_NULL). The data migration step that re-attributes or demotes those channels updates the FK column via ORM.save()calls, which queues deferred constraint trigger events in PostgreSQL. The subsequentALTER TABLE ... DROP NOT NULLon the same table then fails withObjectInUse: cannot ALTER TABLE because it has pending trigger events. Fixed by issuingSET CONSTRAINTS ALL IMMEDIATEat the end of the data migration function to flush those pending events before the DDL runs. (Fixes #1259)stream_xcpreviously treated any extension other than.mp4as a forcedmpegtsrequest, including the empty-extension URLs that XC-compatible M3U playlists produce viaget.php. Requests with no extension now passforce_format=Noneso the standard resolution chain (request param, user default, server default) applies correctly.get.phpM3U playlist previously emitted bare/live/user/pass/idURLs with no query string, causing per-user and server-wide output profile and output format settings to be silently ignored for XC clients. Whenoutput_profileoroutput_formatparameters are present on the playlist request, they are now appended to every stream URL in the playlist so the proxy honours them on playback.Performance
generate_m3upreviously rebuilt the query-string suffix (and for XC requests, calledbuild_absolute_uri_with_port) on every channel iteration even though both inputs are request-level constants. The XC base URL and both query-string suffixes (xc_qs_suffix,proxy_qs_suffix) are now computed once before the channel loop; per-channel URL assembly is a single f-string interpolation.Configuration
📅 Schedule: (in timezone America/New_York)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.