archivr-qa d0e8e8beef ci: bump yt-dlp from upstream releases, not nixpkgs ... The flake no longer takes yt-dlp from nixpkgs; a dedicated `ytDlp` derivation fetches the upstream release binary directly and pins both `version` and an SRI `hash`. That makes the previous workflow inert: it ran `nix flake update nixpkgs` and compared `nixpkgs#yt-dlp.version` before and after, so it could churn the lockfile forever without ever moving the version we actually ship. The workflow now reads the pinned version straight out of the `ytDlp` block in flake.nix, asks the GitHub API for yt-dlp's latest release tag, short-circuits when they already match, downloads the new release to recompute its SRI hash (required — the hash is part of the derivation's identity, so the URL cannot be changed alone), and rewrites the three pinned fields under a sed range address scoped to that block so sibling pins like ublockLite and isdcac are untouched. It asserts only flake.nix changed and that the new version appears exactly twice before opening the PR.		2026-08-23 19:21:06 +02:00
..
workflows	ci: bump yt-dlp from upstream releases, not nixpkgs	2026-08-23 19:21:06 +02:00