Repository navigation
fix: a source moved upstream says how to pin it; the canary takes AMF 1.5.3's re-cut - #15
Merged
Merged
Conversation
… 1.5.3's re-cut - A tag that moved, or an archive replaced, upstream told the user to run ffmpeg-build update, but update keeps the pin of a version the lock already has: only deleting the entry and running ffmpeg-build lock takes the new commit or content. Both messages now say just that. - examples/canary: AMD moved AMF's v1.5.3 tag to a re-cut commit (2026-10-16; the public headers only gained definitions), which failed the canary's Windows builds; its lock pins the new commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||
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
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.
Monday's Canary failed its Windows builds: AMD moved AMF's
v1.5.3tag from8c64800to a re-cut57ee0cf(2026-10-16, release re-created; the public headers only gained definitions). The engine refused it, as it should.ffmpeg-build update, but update keeps the pin of a version the lock already has, so only deleting the entry and runningffmpeg-build locktakes the new commit or content. Both messages now say just that; tests pin the wording.🤖 Generated with Claude Code