Repository navigation
Prepare 0.10.0 release - #52
Merged
Merged
Conversation
Rename Unreleased to 0.10.0, add an upgrade checklist for the breaking changes, list the crash fixes first, and move the negotiate_languages bound change from Fixed to Changed.
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.
Bumps the version to 0.10.0 and turns the Unreleased CHANGELOG section into the 0.10.0 release notes.
The notes were written across six PRs, so this also edits them into one coherent section:
with_langneg(), dropping&on&Vec<u8>, prefixed structured accessors, and accessors that are no longer generated for broken translations.load()with more than one language.negotiate_languagesbound change moved from Fixed to Changed.cargo publish --dry-runpackages and verifies 0.10.0. The package has 47 files and no playground or test snapshots, anddocs/*.mdis included because the guides are compiled into the docs.After merging, the release itself is
cargo publishfrommain, then taggingv0.10.0on the merge commit, as withv0.9.0.