Bump to upstream Invidious 2.20260804.1 - #2
Merged
Merged
Conversation
Update the pinned upstream images from the 2026-06-26 release, which was ~6 weeks stale and hitting the recurring upstream YouTube "non 200 status code / status code 400" on the browse path (trending/search). That path is the main Invidious process talking to YouTube's InnerTube API directly -- distinct from the companion, which handles video streams and was working. The fix for this class of break is an upstream release, not a config change: po_token/visitor_data are no longer config fields, and token generation is the companion's job. - Dockerfile: both FROM lines 2.20260626.0 -> 2.20260804.1 (+ -arm64). The .1 is a same-day hotfix of the 2026-08-04 release that only restores debug symbols in the OCI build -- no behavior change, strictly preferable. - Companion: master-5652eda -> 2026.08.03-438c668. Upstream retired the master-<sha> tag scheme around June 2026 in favor of immutable YYYY.MM.DD-<sha> build tags; the pin comment is corrected to match. - current.ts: 2.20260804.1:0 + release notes in all five languages. New upstream version, no data migration, so current.ts is edited in place rather than spun off; VersionGraph handles the in-place upgrade from the installed 2.20260626.0:0. config.yml.ts is unchanged. Diffing upstream config.example.yml across the two releases, the only additions are optional keys with upstream defaults (disable_abusable_api, a videojs buffer block, socks5 proxy support) and all ten keys this package manages still exist -- so nothing mandatory changed. The optional keys are noted in TODO.md as possible future action toggles. Verified: tsc + SDK lint clean, ncc builds, both arches pack, built manifests report version 2.20260804.1:0 / sdkVersion 2.0.6. The three image tags were confirmed present on quay before building. Device-tested by the maintainer as an in-place upgrade over 2.20260626.0_0: the browse path and playback both check out. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Updates the pinned upstream images from the 2026-06-26 release (~6 weeks stale) to the latest upstream release. Motivated by the recurring upstream YouTube "non 200 status code / status code 400" on the browse path (trending/search) — the main Invidious process talking to YouTube's InnerTube API directly, distinct from the companion (video streams), which was working. The remedy for this class of break is an upstream bump, not a config change.
Changes
2.20260626.0→2.20260804.1(+-arm64)..1is a same-day hotfix of the Aug 4 release that only restores debug symbols in the OCI build; no behavior change.master-5652eda→2026.08.03-438c668. Upstream retired themaster-<sha>scheme (~June 2026) for immutableYYYY.MM.DD-<sha>build tags; the pin comment is corrected.2.20260804.1:0+ release notes ×5 languages. New upstream version, no data migration → edited in place;VersionGraphhandles the in-place upgrade from the installed2.20260626.0:0.config.example.ymldelta across the two releases is only optional keys with upstream defaults (disable_abusable_api, avideojsbuffer block, socks5 proxy) and all ten managed keys survive, so nothing mandatory changed. Optional keys noted inTODO.mdas possible future action toggles.Verification
tsc+ SDK lint clean,nccbuilds, both arches pack from a cleared tree; built manifests reportversion 2.20260804.1:0/sdkVersion 2.0.6.2.20260626.0_0— the browse path (trending/search) and playback both check out.🤖 Generated with Claude Code