Repository navigation
release: 0.5.1 - #88
Merged
Merged
Conversation
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.
Before
@versionis 0.5.0.mainholds whisper.cpp 1.9.5 (#87), the Rust 1.99.1 and ROCm 7.2.4 builds (#85), therustler_precompiled ~> 0.10.0requirement (#80), and the language fix for offset windows (#78), which no release carries.Problem
Users of 0.5.0 miss the abort during language detection, two out-of-bounds reads on malformed model files, and the window language fix.
After
@versionsays 0.5.1, and the changelog's Unreleased section becomes 0.5.1. The merge builds the six NIFs and tagsv0.5.1. The checksum PR follows, and its merge publishes to Hex through #86, where the release waits for an owner's approval.Included PRs and the risk
The CUDA, HIP, and Metal builds at whisper.cpp 1.9.5 and ROCm 7.2.4 run first in this release matrix. The tag job does not wait for the builds, so when one build fails,
v0.5.1exists without a GitHub release. Then we fix the cause and run the manual dispatch ofrelease.ymlforv0.5.1, asAGENTS.mdsays.The README's
~> 0.5.0covers 0.5.1.