Full Docker Hub tag census: 1.43.5.11029-…-ls329 is the newest version and newest ls build on the channel (Plex 1.43.4.10903 -> 1.43.5.11029 is two releases ahead of the live pin).
Digest proof at pin time: the tag's manifest digest equals the registry's current latest — sha256:8f655bad7dcbc5398a78f70a5af12600b4ed3424f901566ed1eaa6710e9e2334 (the verification law the Plex page already records; wording there corrected from a stale "ghcr" to the registry actually used).
Impact
Quadlet restart => PMS runs its usual one-minor DB migration on first boot; the deployer's /identity-over-HTTPS gate already tolerates the slow first boot (600 s).
No config/volume/network changes. Rollback = revert one line.
Evidence
./tests/run.sh — 488/488 pass.
Deploy (on your OK): deploy.sh dankserver --service plex, then verify the container reports 1.43.5.11029 via /identity.
## What
One-line image bump: `lscr.io/linuxserver/plex:1.43.4.10903-e5521bd8c-ls325` -> **`1.43.5.11029-6bf8af3f0-ls329`**.
## Why it's the latest
- Full Docker Hub tag census: `1.43.5.11029-…-ls329` is the newest version and newest ls build on the channel (Plex 1.43.4.10903 -> 1.43.5.11029 is two releases ahead of the live pin).
- **Digest proof at pin time:** the tag's manifest digest equals the registry's current `latest` — `sha256:8f655bad7dcbc5398a78f70a5af12600b4ed3424f901566ed1eaa6710e9e2334` (the verification law the Plex page already records; wording there corrected from a stale "ghcr" to the registry actually used).
## Impact
- Quadlet restart => PMS runs its usual one-minor DB migration on first boot; the deployer's `/identity`-over-HTTPS gate already tolerates the slow first boot (600 s).
- No config/volume/network changes. Rollback = revert one line.
## Evidence
- `./tests/run.sh` — 488/488 pass.
- Deploy (on your OK): `deploy.sh dankserver --service plex`, then verify the container reports 1.43.5.11029 via `/identity`.
---
cwd: /home/blank/.omp/wt/wt-20261020-125416-6d1fc1f · session: 01a15b5c-ede9-7063-b05b-1ef94188b7c3
(build worktree: /tmp/wt-plex)
ls329 is the newest build on the linuxserver channel and Plex 1.43.5.11029
is their newest release; the live pin (ls325 / 1.43.4.10903) is two Plex
releases behind. Digest-verified at pin time: the tag's manifest digest
equals the registry's current 'latest' (sha256:8f655bad...e9e2334), the
same law the page records. Quadlet restart runs PMS's usual one-minor
schema migration on first boot; the deployer's /identity HTTPS gate
tolerates the first-boot migration up to 600 s.
Rollback: revert this commit (one line).
dank
merged commit 656d9567d5 into main2026-10-21 00:07:28 -07:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
One-line image bump:
lscr.io/linuxserver/plex:1.43.4.10903-e5521bd8c-ls325->1.43.5.11029-6bf8af3f0-ls329.Why it's the latest
1.43.5.11029-…-ls329is the newest version and newest ls build on the channel (Plex 1.43.4.10903 -> 1.43.5.11029 is two releases ahead of the live pin).latest—sha256:8f655bad7dcbc5398a78f70a5af12600b4ed3424f901566ed1eaa6710e9e2334(the verification law the Plex page already records; wording there corrected from a stale "ghcr" to the registry actually used).Impact
/identity-over-HTTPS gate already tolerates the slow first boot (600 s).Evidence
./tests/run.sh— 488/488 pass.deploy.sh dankserver --service plex, then verify the container reports 1.43.5.11029 via/identity.cwd: /home/blank/.omp/wt/wt-20261020-125416-6d1fc1f · session: 01a15b5c-ede9-7063-b05b-1ef94188b7c3
(build worktree: /tmp/wt-plex)