Repository navigation
chore: release v0.3.1 - #27
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.
Docs-only patch release so the crates.io page stops showing the rustdoc hidden lines.
The 0.3.0 README wrote its example fences in rustdoc hidden-line style (
# use ...prefixes that rustdoc strips in rendered docs). crates.io renders crate READMEs as plain markdown and prints every one of those lines, which buried the Quick start under a wall of#. Master already carries the fixed, self-contained snippets (from #26 and the dehash work before it); this release is what gets them onto crates.io, since the page renders the README packaged with the latest published version.Details are in the new CHANGELOG section. Gates all pass:
cargo test --all-features,cargo clippy --all-features --all-targets -- -D warnings,cargo doc --all-features --no-deps. No runtime code changed since v0.3.0, only test modules and docs.Merging triggers the Changelog Release workflow as usual: version bump and literal sync, tag, GitHub Release,
cargo publishof gpui-query 0.3.1, then the web deploy. The satellites stay at 0.1.0; they are already on the index and the workflow skips them.