chore(tools): bump pinned yt-dlp to 2026.08.19 - #35
Closed
github-actions[bot] wants to merge 1 commit into
Closed
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
added
the
dependencies
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.
yt-dlp released
2026.08.19; MicMixer pins2026.07.04.The pinned version and its SHA-256 in
src/MicMixer/Music/ToolBootstrapper.cswere updated.The checksum was taken from
yt-dlp.exeof that release after running it andconfirming it reports
2026.08.19. The version marker file makes existinginstalls re-download the tool by themselves.
Upstream release notes: https://github.com/yt-dlp/yt-dlp/releases/tag/2026.08.19
Merging this touches
src/**and therefore publishes a new MicMixer release,so update
RELEASE_NOTES.mdfirst if this release needs its own entry.Note that pull requests opened with the built-in workflow token do not start
CI. The release workflow runs the full test suite before it publishes, so a
bad merge fails there rather than shipping.