Repository navigation
Prepare alpha 4 for crates.io with verified publication steps - #6
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.
Prepare the first crates.io release so consumers can use
edit-session = "=0.1.0-alpha.4". This is an unpublished candidate: the API, behavior, Rust 1.88 minimum and zero runtime dependencies are unchanged, and existing alpha.3 release files stay intact.Enables only the
crates-ioregistry, adds a package landing page with absolute links, and makes CI runcargo publish --dry-run. The manual publication workflow defaults to validation and saves a verified crate/checksum; uploads require a matching version tag in main and thecrates-ioenvironment. Later releases use OIDC. The guide documents the separate token-based first upload required by crates.io. No registry upload or account setup is performed by this PR.Validation: 16 lifecycle tests, 8 recovery tests, 1 compile-fail doctest; retry example; fmt, strict Clippy and rustdoc;
cargo publish --dry-run --locked --registry crates-io; actionlint; branch and mismatched-tag rejection checks. CI verifies Rust 1.88 and stable.