ersatztv

Author	SHA1	Message	Date
timothy	81996709b0	chore(release): re-trigger PR CI for v26.14.0 Prior attempts on this branch produced no pull_request run: two CLI pushes, a close/reopen, and a body edit all yielded nothing, and the workflow_dispatch I fired (run 1564) went green but writes NO commit statuses, so it cannot satisfy the required Build & test / review-verdict/h10 checks. The queue is now idle (run 1560, main @ `a2b3a56d9`, completed success), which is the condition docs/ci-cd.md says matters -- back-to-back pushes get silently dropped, a spaced-out one does not. No [skip ci] token -- this branch's merge commit is the v26.14.0 tag target.	2026-08-05 00:30:55 +02:00
timothy	7b20dbd360	docs(release): fold #674/#688 into the v26.14.0 notes after rebasing on main main moved while this branch was open: #725 (fix/674-688-decisions-validator) merged, so v26.14.0 now also carries the decisions-validator PyYAML cross-check. Rebased onto `a2b3a56d9` rather than merging main in, per release.format-as-you-touch-rebase. The added claim is verified, not assumed: re-breaking this release's own readrate-catchup record (unquoting rule: so an unquoted " #350" truncates it) now fails decisions_validate with frontmatter key 'rule' means different things to the two parsers ... PyYAML wrote this file, so its reading is the real value and the record is silently corrupt. Common cause: an unquoted ` #` ... which is exactly the defect that reached CI earlier in this session (`57ad5efb3`) because the pre-#725 validator could not see it. Local gate now catches it. scripts/tests: 432 passed (was 411 before #725 added its cases). No [skip ci] token -- this branch's merge commit is the v26.14.0 tag target.	2026-08-04 23:49:35 +02:00
timothy	e997668ac4	chore(release): re-trigger CI for v26.14.0 release notes The release/v26.14.0 push produced NO ActionRun records at all -- verified against 7168 listed tasks, zero for `b48f44dc7`. This is the documented Gitea behavior in docs/ci-cd.md: several pushes fired back-to-back (the #737 merge, then this branch, then the PR open) and the later events were silently dropped. The remedy is a spaced-out re-push, not assuming the runner is broken. No [skip ci] token -- this branch's merge commit is the v26.14.0 tag target.	2026-08-04 23:47:11 +02:00
timothy	9a3371ecd9	docs(release): record the v26.14.0 release notes Headline is ersatztv#726: Live TV stalled on any item carrying an embedded PGS/DVD bitmap subtitle, because -readrate paces an input off its furthest-behind stream and that sparse subtitle shares the video's own -i. Fixed with a capability-gated -readrate_catchup rather than the structural change the issue originally proposed, which would have removed the throttle from the frame-producing path that ffmpeg.qsv-extra-hw-frames-floor depends on. Also in this release: the H10 review-verdict gate's raced-sentinel false-open (#706/#707/#711), and two Renovate dependency bumps. No [skip ci] token -- this commit is the release tag target, and Gitea reads skip-ci from the TAGGED commit, which would suppress the release build. Refs #726	2026-08-04 23:47:11 +02:00

Compare commits

Diff Content Not Available