Repository navigation
release: 0.6.0 - #83
Merged
Merged
Conversation
rubas
force-pushed
the
release/0.6.0
branch
from
September 23, 2026 12:16
938a827 to
da9d147
Compare
Owner
Author
|
Review findings for the 0.6.0 release:
|
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.
Version 0.6.0.
Why
rubas/rsmpegfork. The fork supports FFmpeg 9 and has theAVChannelLayoutfix, so thecopy_ch_layoutworkaround is gone.EXMPEG_BUILD=1) now need FFmpeg 9. This breaks source builds against FFmpeg 8, so this is a minor release.The 0.5.0 entry in
CHANGELOG.mdstays as it is. Its Hex publish still waits for the owner.Included PRs
What changed
mix.exs:@version "0.6.0".CHANGELOG.md: new 0.6.0 entry from the Changelog section of feat: build on FFmpeg 9.0.1 through our rsmpeg fork #82, checked against its diff. The file had no Unreleased section.README.md: the install snippet is now{:exmpeg, "~> 0.6"}. No other doc names the version.checksum-Elixir.Exmpeg.Native.exskeeps the v0.5.0 entries. Step 3 ofRELEASE.mdreplaces them after the release workflow tags v0.6.0.Decisions
rsmpegresolves from crates.io and that a source build no longer fetches from GitHub. feat: build on FFmpeg 9.0.1 through our rsmpeg fork #82 made that untrue. The brief keeps the 0.5.0 entry as it is, so the 0.6.0 entry states the reversal.copy_ch_layoutis not in the changelog. Callers see no change: the 0.5.0 fix for the channel layout crash stays in effect through the fork.chore: release X.Y.Zstyle of release: 0.5.0 #78. The PR title follows the brief.Checks
With
. /tmp/elixir-sweep/exmpeg-env9.sh(Arch system FFmpeg 9.0.1, libclang 20,EXMPEG_BUILD=1):task check: green (format, compile--warnings-as-errors, credo strict with no issues, clippy-D warnings, 43 Elixir unit tests, 17 Rust tests, zizmor with no findings).task test:integration: 104 passed.dprint.jsonin the repository, sodprint fmtdid not run.