jlab-cluster/helm-charts
3
0 Fork 0
Code Issues 15 Pull Requests 3 Actions Packages Wiki Activity

Update docker.io/linuxserver/qbittorrent Docker tag to v5.2.4
renovate/stability-days Updates have not met minimum release age requirement
Details
Validate Helm Charts / Detect changed charts (pull_request) Successful in 3s
Details
Validate Helm Charts / Resource quantities (pull_request) Successful in 8s
Details
Validate Helm Charts / Selector match (pull_request) Successful in 8s
Details
Validate Helm Charts / Build freesailarr (pull_request) Successful in 4s
Details
Validate Helm Charts / Trivy config freesailarr (pull_request) Successful in 10s
Details
Install-test / Install-test freesailarr (pull_request) Successful in 2m54s
Details
Validate Helm Charts / Install-test (pull_request) Successful in 2m54s
Details

Browse Source
This commit is contained in:
jlab-renovate-bot committed 2026-10-11 12:05:21 +00:00
1 parent b5b5d9a310
commit 12e073d6a6
2 files changed
+2 -2
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

freesailarr/Chart.yaml
+1 -1
View File
@@ -8,7 +8,7 @@ description: A Helm chart to deploy a Wireguard-tunneled media automation stack
type: application type: application
version: 3.1.1+up1.0.0 version: 3.1.2+up1.0.0
# The chart's own version marker, freely chosen and tied to no upstream. The # The chart's own version marker, freely chosen and tied to no upstream. The
# stack bundles ten independently versioned projects (nine of them on by # stack bundles ten independently versioned projects (nine of them on by
# default), so there is no single "app version" to track here. # default), so there is no single "app version" to track here.
freesailarr/values.yaml
+1 -1
View File
@@ -343,7 +343,7 @@ qbittorrent:
enabled: true enabled: true
image: image:
repository: docker.io/linuxserver/qbittorrent repository: docker.io/linuxserver/qbittorrent
tag: 5.2.3 tag: 5.2.4
# Every app gets its own Ingress object (named <release>-<chart>-<app>-ingress) # Every app gets its own Ingress object (named <release>-<chart>-<app>-ingress)
# with its own TLS secret tls-<release>-<chart>-<app>-ingress, so the apps can # with its own TLS secret tls-<release>-<chart>-<app>-ingress, so the apps can
# be exposed independently and under unrelated hosts. # be exposed independently and under unrelated hosts.