Publish shuttle-tokio-impl-inner 0.1.2 - #341
Open
sarsko wants to merge 1 commit into
Open
Conversation
The mpsc reservation APIs (#340) and `Receiver::poll_recv` (#319) both landed in shuttle-tokio-impl-inner, which still declared 0.1.1 -- already on crates.io, so it could not be published. Only this crate needs a new version. `shuttle-tokio-impl` 0.1.1 requires inner as `^0.1.1` and re-exports it with `pub use shuttle_tokio_impl_inner::*`, and `shuttle-tokio` 1.0.0 requires impl as `^0.1.1`, so both published crates pick 0.1.2 up on resolution without a republish. Neither crate's own sources have changed since they were published. Also record #319 in the changelog, which was missing an entry.
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.
The mpsc reservation APIs (#340) and
Receiver::poll_recv(#319) both landed inshuttle-tokio-impl-inner, which still declared 0.1.1 — already on crates.io, so it can't be published.Only this crate needs a version
shuttle-tokio-impl0.1.1 requires inner as^0.1.1and re-exports it withpub use shuttle_tokio_impl_inner::*, andshuttle-tokio1.0.0 requires impl as^0.1.1.^0.1.1admits 0.1.2, and the glob picks up the new items, so both published crates get the new APIs on resolution without a republish. Neither crate's own sources have changed since they were published, so bumping them would upload identical content.0.1.2 rather than 0.2.0 for the
Permit<T>→Permit<'a, T>change: the only way to obtain aPermitwasreserve, which panicked withunimplemented!(), so nothing can have been relying on the old shape.Also in 0.1.2
Receiver::poll_recv(#319) was missing a changelog entry; added. The only other inner change since 0.1.1 is two iteration counts inwatch.rs'smod tests(#320), which isn't user-visible.Testing
cargo package -p shuttle-tokio-impl-inner— packages and verifies clean, building against the publishedshuttle 0.9.3, so this needs no newshuttlerelease.cargo nextest run --release -p shuttle-tokio-impl-inner— 112 passed, 1 skipped.