Skip to content

ci: re-pin FFmpeg to a live BtbN autobuild - #8

Merged
ksindi merged 1 commit into
mainfrom
fix/ffmpeg-autobuild-repin
Aug 3, 2026
Merged

ci: re-pin FFmpeg to a live BtbN autobuild#8
ksindi merged 1 commit into
mainfrom
fix/ffmpeg-autobuild-repin

Conversation

@ksindi

@ksindi ksindi commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

CI (and the perf workflow) fail at the Install FFmpeg 7.1 (shared) step with a curl 404: the pinned autobuild-2026-07-09-14-21 release no longer exists — BtbN prunes dated autobuild releases after a few weeks.

This re-pins to the newest autobuild, autobuild-2026-08-02-13-17 (ffmpeg-n7.1.5-12-g1fdbca85aa-linux64-gpl-shared-7.1, same flavor as before), with a freshly verified sha256, and adds a comment noting the pruning behavior so the next 404 is a quick re-pin.

Note: this will recur every few weeks as long as we pin to BtbN autobuilds. If that gets annoying, the durable fix is to mirror the tarball to infrastructure we control (e.g. a GCS bucket or a repo release asset) and download from there. release.yml uses the latest alias (no checksum) and is unaffected.

BtbN prunes dated autobuild releases after a few weeks, so the pinned
autobuild-2026-07-09-14-21 release now 404s and the 'Install FFmpeg'
step fails in CI and perf workflows. Re-pin to autobuild-2026-08-02-13-17
(ffmpeg n7.1.5-12, same linux64-gpl-shared-7.1 flavor) with its verified
sha256, and note the pruning behavior next to the pin.
@upwind-code-us

upwind-code-us Bot commented Aug 3, 2026

Copy link
Copy Markdown

Upwind Upwind Code Scan - ✅ Proceed with Deployment

0 newly introduced vulnerabilities · 0 resolved · 1 total in this PR vs main

🟡 1 Medium

View full analysis in Upwind Console

Scan completed in 16s

Scan history (3 scans)
Commit Scanned at New Resolved Net
b0da3c1 2026-07-06 17:32 UTC
2225812 2026-07-06 22:32 UTC
3681b5b < 2026-08-03 11:53 UTC 0 0 0

Last scanned: 3681b5b · 2026-08-03 11:53 UTC

@upwind-code-us

upwind-code-us Bot commented Aug 3, 2026

Copy link
Copy Markdown

Upwind Upwind IaC Scan - ✅ Proceed with Deployment

0 newly introduced misconfigurations · 0 resolved · 0 total in this PR vs main

View full analysis in Upwind Console →

Scan completed in 5s

Scan history (3 scans)
Commit Scanned at New Resolved Net
b0da3c1 2026-07-06 17:32 UTC
2225812 2026-07-06 22:32 UTC
3681b5b < 2026-08-03 11:53 UTC 0 0 0

Last scanned: 3681b5b · 2026-08-03 11:53 UTC

@ksindi
ksindi merged commit 655417d into main Aug 3, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant