Repository navigation
Set the version to 0.1.1 - #12
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
What changes
The version of the three crates is 0.1.1 (
[workspace.package]and the dependency onthirtys3-corein the rootCargo.toml, and the lock file), as the Release workflow wants before it publishes. The README says "version 0.1" and no longer names the patch number.0.1.1 is a repair release of 0.1.0. What it has that 0.1.0 does not:
rustls-webpki0.103.16,ctutils0.4.6,tokio1.54.1), and the crates ask fortokio1.54.1 at least, so no build resolves to the yanked 1.54.0;No code of the libraries changes.
How it was tested
cargo package --workspace --lockedbuilds the three packages at 0.1.1. The checks of this pull request are the rest.Checklist
maintenancecompatibilitypage and the documentation do not need changes