v1.3.0

Highlights

Cooperative batch boundaries

Generated machines now implement IBoundaryMachine<TValue>. Use FireUntilBoundaryAsync when an action or hook can call RequestBatchBoundary() after changing an outside condition—such as the decoder that must process the rest of a network buffer. The method reports how many values were consumed, leaving the caller responsible for the unconsumed suffix.

Existing IMachine<TValue>.FireAsync behavior is unchanged: it ignores cooperative boundary requests and consumes the complete batch. The new capability is additive.

Truthful generated diagrams

Mermaid and Dot diagrams now draw every decision outcome and its target. Mermaid output also emits composite children before leaf siblings so generated diagrams parse reliably. The documented examples include diagrams checked against each machine definition.

Contribution and release guidance

The repository now includes contribution guidance, issue and pull-request templates, and explicit security-release changelog requirements.

See CHANGELOG.md for the complete release notes and Runs for a consumer example.

Full changelog: v1.2.0...v1.3.0

v1.2.0

What's Changed

• Create FUNDING.yml by @HarryCordewener in #5
• Bump the roslyn group with 2 updates by @dependabot[bot] in #1
• Pin the package graph with lock files, and name a code owner by @HarryCordewener in #4
• Bump Stateless and Verify.TUnit by @dependabot[bot] in #3
• Bump the actions group with 3 updates by @dependabot[bot] in #2
• Fix main: every target framework back in the lock files by @HarryCordewener in #7
• Give the suspension ceiling room a compiler change cannot use up by @HarryCordewener in #6
• Build against Roslyn 4.8 again, and test the floor instead of asserting it by @HarryCordewener in #8

New Contributors

• @HarryCordewener made their first contribution in #5
• @dependabot[bot] made their first contribution in #1

Full Changelog: v1.0.1...v1.2.0