feat(container): update image ghcr.io/dmunozv04/isponsorblocktv ( v2.6.1 → v2.8.1 )#2944
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
feat(container): update image ghcr.io/dmunozv04/isponsorblocktv ( v2.6.1 → v2.8.1 )#2944renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
--- kubernetes/berries/apps/media/isponsorblocktv/app Kustomization: flux-system/cluster-apps-isponsorblocktv HelmRelease: media/isponsorblocktv
+++ kubernetes/berries/apps/media/isponsorblocktv/app Kustomization: flux-system/cluster-apps-isponsorblocktv HelmRelease: media/isponsorblocktv
@@ -26,13 +26,13 @@
containers:
app:
env:
TZ: Europe/Moscow
image:
repository: ghcr.io/dmunozv04/isponsorblocktv
- tag: v2.6.1
+ tag: v2.8.1
probes:
liveness:
enabled: false
readiness:
enabled: false
startup: |
--- HelmRelease: media/isponsorblocktv Deployment: media/isponsorblocktv
+++ HelmRelease: media/isponsorblocktv Deployment: media/isponsorblocktv
@@ -40,13 +40,13 @@
hostPID: false
dnsPolicy: ClusterFirst
containers:
- env:
- name: TZ
value: Europe/Moscow
- image: ghcr.io/dmunozv04/isponsorblocktv:v2.6.1
+ image: ghcr.io/dmunozv04/isponsorblocktv:v2.8.1
name: app
resources:
limits:
memory: 200M
requests:
cpu: 100m |
renovate
Bot
force-pushed
the
renovate/ghcr.io-dmunozv04-isponsorblocktv-2.x
branch
from
acc5f9b to
d1bc13b
Compare
…6.1 → v2.8.1 ) | datasource | package | from | to | | ---------- | --------------------------------- | ------ | ------ | | docker | ghcr.io/dmunozv04/isponsorblocktv | v2.6.1 | v2.8.1 |
renovate
Bot
force-pushed
the
renovate/ghcr.io-dmunozv04-isponsorblocktv-2.x
branch
from
d1bc13b to
ece184f
Compare
renovate
Bot
changed the title
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:
v2.6.1→v2.8.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
dmunozv04/iSponsorBlockTV (ghcr.io/dmunozv04/isponsorblocktv)
v2.8.1: : WARNING: YouTube is revoking old screen IDs, your device might have stopped workingCompare Source
Warning
YouTube has changed the screen ID format from 26 characters to 64 hex digits. Since the 15th April 2026 YouTube apps have started generating new IDs and revoking the old ones, breaking a paired iSponsorBlockTV.
The solution is simple, pairing the device again will (most likely) fix this.
Read more info on #450 and https://github.com/dmunozv04/iSponsorBlockTV/wiki/new-screen-ID-format
What's Changed
Full Changelog: dmunozv04/iSponsorBlockTV@v2.7.0...v2.8.1
v2.8.0: : WARNING: YouTube is revoking old screen IDs, your device might have stopped workingCompare Source
Warning
YouTube has changed the screen ID format from 26 characters to 64 hex digits. Since the 15th April 2026 YouTube apps have started generating new IDs and revoking the old ones, breaking a paired iSponsorBlockTV.
The solution is simple, pairing the device again will (most likely) fix this.
Read more info on #450 and https://github.com/dmunozv04/iSponsorBlockTV/wiki/new-screen-ID-format
What's Changed
Full Changelog: dmunozv04/iSponsorBlockTV@v2.7.0...v2.8.0
v2.7.0: : UX improvements releaseCompare Source
Main Changes
Improvements to setup messages, now respecting empty skip categories
What's Changed
New Contributors
Full Changelog: dmunozv04/iSponsorBlockTV@v2.6.1...v2.7.0
Configuration
📅 Schedule: (in timezone Europe/Moscow)
🚦 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.