Consume published CatHub protocol packages#552
Merged
Conversation
17 tasks
rtreit
marked this pull request as ready for review
July 23, 2026 21:44
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.
QsoRipper now consumes CatHub protocol version 0.1.1 from crates.io and NuGet.
The Rust engine uses
cathub-protocol. The .NET engine usesCatHub.Protocol. This change removes the duplicated WinKeyer broker proto snapshot and its comparison script. The integration guide now identifies CatHub as the protocol source.The wire package remains
qsoripper.servicesfor CatHub 0.1 compatibility.Validation:
build.ps1 checkpassed. The focused Rust CW tests passed with 24 tests. The focused .NET CW tests passed with 16 tests. Buf lint passed.Parent issue: #540
Closes #551