Prepare the 0.11.0 release - #51
Merged
Merged
Conversation
The library and its three members move to 0.11.0, `Unreleased` becomes the dated 0.11.0 section with its compare link, and the two places the site writes the version by hand -- the landing page's eyebrow and the versioning note on the docs index -- say 0.11.0. A breaking release: `Config` holds a `SchemaSource` and loses its `nodes` and `tags` fields, with the migration written out in the changelog. The rest is additive -- `TagRenderer`, the shared schema vocabulary, the command-line host -- and the conformance count is unchanged at 95 green, 10 annotated. `release.sh --dry-run` passes every gate, the MSRV lane on 1.96, the package listing and a publish dry run; `build-npm.sh --pack` builds and packs the npm package at 0.11.0. Nothing is published by this change.
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.
Version bump and changelog only. Nothing is published by this PR; the publish (
release.shonmain, thenbuild-npm.sh --publish) is a separate act after it merges.What changed
Cargo.tomland the three members:0.10.0→0.11.0.Cargo.lockfollows.CHANGELOG.md:Unreleasedbecomes## [0.11.0] - 2026-09-12— fourAddedentries (TagRenderer, the schema vocabulary crate, the command-line host, one workspace lint block) and oneChanged, marked breaking, with theConfigmigration written out.Unreleasedstays as an empty heading; the compare links are updated.0.11.0changed.Why it is 0.11.0 and not 1.0.0
Configchanged shape — a breaking change, permitted at0.xand stated as such in the changelog. The docs index's versioning section says the API has had no external users yet, which is still true.Verified
.github/scripts/release.sh --dry-run: every gate on stable, the library on 1.96 in both feature lanes, the package listing (README present,reference/excluded,spec/included), andcargo publish --dry-run— pass. The script's two soft warnings (not onmain, tree dirty) are what a dry run from the release branch is documented to produce../scripts/build-npm.sh --pack: builds and packsaccent-proust@0.11.0; the member and library versions agree.v0.11.0.Conformance is unchanged at
95 green, 10 annotated, 0 failing (of 105).