Repository navigation
chore(release): 0.5.0 - #199
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests.
... and 1 file with indirect coverage changes 🚀 New features to boost your workflow:
|
joaquinbejar
commented
Oct 20, 2026
joaquinbejar
left a comment
Owner
Author
There was a problem hiding this comment.
APPROVE. All 44 CI checks pass on the reviewed head, including tests, coverage, docs, lint, examples, Docker builds and semver. Workspace versions, internal dependencies, publish order and README snippets are consistent at 0.5.0. The documentation link is corrected. No findings. Submitted as COMMENT because GitHub prevents the author account from approving its own pull request.
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.
Summary
The last PR of the October 2026 issue programme: every workspace crate moves to 0.5.0 (
make version VERSION=0.5.0). The programme carries breaking changes against 0.4.1, so this is a minor bump under 0.x semver. No issue or PR is left open.What 0.5.0 contains
The work merged since 0.4.1 (#99 through #198), among it:
FileStore(Make MessageStore sequence persistence fallible and add a fail-closed write policy (store, engine) #62, Add a persistent file-backed MessageStore (store) #78, FileStore: writer thread, dense index, counter slots and compaction (store) #112);NextExpectedMsgSeqNumon Logon (Support NextExpectedMsgSeqNum (789) on Logon in both roles (engine) #79), the gap queue (Optionally queue out-of-order application messages during a gap (engine) #71), garbled-frame recovery (Ignore garbled inbound frames without consuming MsgSeqNum instead of closing the session (transport, engine) #66);tlsfeature (Add optional TLS for initiator and acceptor via rustls (engine) #81), inbound dictionary validation (Validate inbound application messages against a dictionary on the session path, with an Off/Log/Reject policy (engine, dictionary) #84).Public / contract impact
Breaking against 0.4.1 by design. Among the breaks:
#[non_exhaustive]SessionConfig(#66), the fallible async store trait (#62) and the non-exhaustive dictionary schema structs (#106).semver.ymlchecks 10 packages against their crates.io 0.4.1 baseline (notironfix-derive, which it does not support, norironfix-sofh/ironfix-fixp, which have no published baseline yet), and a 0.5.0 version permits these breaks.Nothing is published by this PR.
cargo publish/make publish-allruns only after the owner confirms.Testing
cargo test --workspace --all-features2657 passed, 0 failed; fmt, clippy-D warnings,make doc, check-spanish andcargo build --release --workspaceall clean, with zero warnings.