Repository navigation
Prepare edit-session 0.1.0-alpha.5 with packaged context checks - #10
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.
Package the new context walkthrough and feedback-driven documentation as alpha.5. Public API, runtime behavior, Rust 1.88 minimum and zero runtime dependencies remain unchanged.
The publish workflow now runs the context example and checks its generated diagram both in the checkout and in the extracted crate, alongside the existing recovery example and packaged tests. Earlier release tags and archives remain untouched.
Validation on Rust 1.88: 16 lifecycle tests, 8 recovery tests and one compile-fail doctest; context walkthrough, generated diagram, fmt and strict all-target Clippy pass. The packaged crate builds and its tests, both examples and diagram check pass. This PR prepares the owner-requested alpha publication through the already-configured Trusted Publisher after green release-commit CI.