Repository navigation
docs: prepare 0.2.0 migration and release notes - #2
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
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.
Document the 0.1.4 → 0.2.0 upgrade with before/after initialization, typed errors, metadata and manual includes. Format the changelog using Keep a Changelog, link the migration from README/Rustdoc, and prepare registry dependency recipes.
Remove branch and prerelease-status banners from the public guides. Keep pending changes under Unreleased in the changelog. Ignore changelog-only branch pushes and PRs in CI; mixed changes, tags and manual runs still run checks.
Validation: three independent Rust consumer variants extracted from the migration compiled and ran; package inventory includes the migration and changelog; local Markdown links, formatting and denied-warning Rustdoc passed. Registry-only installation remains a publication-stage check. No tags or crates.io uploads.