Conversation
Published shuttle-async-stream 0.3.6 and shuttle-async-stream-impl 0.1.0 for the first time, and shuttle-lazy_static-impl 0.1.1. No version bumps were needed: the async-stream crates had never been uploaded, and the lazy_static-impl bump had been sitting in the tree since #268. shuttle-lazy_static 1.5.0 requires its impl crate as ^0.1.0, so it picks up 0.1.1 without being republished.
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.
Three crates were unpublished and needed no version bump, so they went out as-is:
shuttle-async-stream-implshuttle-async-streamshuttle-lazy_static-implcargo packageverified both impl crates against the published dependency graph before upload (they resolveshuttle 0.9.3from the registry), so no newshuttlerelease is needed.shuttle-lazy_static1.5.0 requires its impl crate as^0.1.0and so picks up 0.1.1 without being republished — the same mechanism that let #341 shipshuttle-tokio-impl-inner0.1.2 alone.This PR only records that in the CHANGELOG; the crates are already live.
Still unpublished, deliberately left out
Content that has drifted from its published version and therefore needs a version bump before it can go out:
shuttle-engine0.1.1 —future/batch_semaphore.rs,annotations/mod.rs,lib.rs,runtime/task/mod.rsshuttle-std0.1.1 —future.rsshuttle-tokio-macros-impl0.1.0 —src/lib.rs, plus a new READMEshuttle0.9.3 — tests only, nosrc/changeThe first two are the code behind the entries still under
# Unreleased, so releasing them is theshuttlerelease, not a wrapper publish. Holding it seemed right rather than shipping half of# Unreleased.Separately, fourteen crates differ from their published version only in packaging metadata (the
repositoryfield from #329, READMEs from #315, and theCHANELOG.md→CHANGELOG.mdrename inshuttle-parking_lot-impl). Republishing those would mean fourteen version bumps to change nothing but crates.io metadata, so they are left alone; they can ride along the next time each crate has a real change.