Repository navigation
Release 0.9.1 - #74
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.
Version 0.9.1, collecting what merged since 0.9.0: the latency check reads the impulse's arrival against the response's peak, so a plugin with a fractional-delay leak one frame early is no longer refused by one frame; and CI checks the pins file against the published plugin-hostd.
A patch: a fix, and no consumer's floor depends on it (omx-plugins' release gate installs the newest plugin-qualify and reads only the real-time-safety verdict). Dependency floors are unchanged.
package.json, the RPM spec and debian/changelog agree on 0.9.1. The repository has no version-check target, so this was checked with the release train's own version_files reader on the commit: 0.9.1 across all three; a commit with package.json alone at 0.9.2 read DISAGREE.