ci: source pinned ffmpeg from immutable GitHub release (durable fix)#137
Merged
Conversation
The "Download ffmpeg (pinned)" step in ci.yml (bundle-smoke) and release.yml pulled from gyan.dev/ffmpeg/builds/packages/, which only hosts the single latest version-pinned build. When gyan.dev bumped its latest, the old version-pinned URL 404'd — silently returning an HTML error page that failed Invoke-WebRequest — breaking bundle-smoke and the release build (this happened with 8.1.1 -> 8.1.2 in 2026-07). Switch the source to GyanD/codexffmpeg GitHub releases, which publishes the identical "essentials" builds gyan.dev serves but keeps every version tag as immutable release assets. The pinned zip is byte-identical (verified: same SHA-256 db580001... that gyan.dev publishes), so nothing about the shipped ffmpeg binary changes — only the download host. The URL now never disappears on its own; the pin changes only when we deliberately bump it. Validated on real Windows PowerShell: Invoke-WebRequest (302 -> GitHub asset CDN) downloads, SHA-256 matches, Expand-Archive yields bin/ffmpeg.exe, and `ffmpeg -version` reports 8.1.2-essentials_build-www.gyan.dev. Infra-only (workflow files); no code or shipped-bundle change, no version bump. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Why
The
Download ffmpeg (pinned)step inci.yml(bundle-smoke) andrelease.ymlpulled fromgyan.dev/ffmpeg/builds/packages/, which only hosts the single latest version-pinned build. When gyan.dev bumps its latest, the previous version-pinned URL starts returning a 404 HTML page (which failsInvoke-WebRequest), silently breaking bundle-smoke and the release build. This is exactly what happened when 8.1.1 → 8.1.2 rotated (2026-07), and it would recur on every future gyan.dev bump.What
Repoint both workflows to GyanD/codexffmpeg GitHub releases — the same author's identical "essentials" builds, but published as immutable, permanently-retained GitHub release assets.
db580001…) gyan.dev publishes, so nothing about the shipped ffmpeg changes — only the download host. Kept the existing SHA-256 pin.Infra-only change (two workflow files). No source or shipped-bundle change, no version bump, no release needed.
Validation
Ran the exact step logic on real Windows PowerShell:
Invoke-WebRequest(302 → GitHub asset CDN) downloads, SHA-256 matches,Expand-Archiveyieldsbin/ffmpeg.exe, andffmpeg -versionreports8.1.2-essentials_build-www.gyan.dev. The bundle-smoke check on this PR exercises the new path end-to-end.🤖 Generated with Claude Code