bump rusty_alloc-api to =2.2.0 - #8
Open
Ttimmahlax wants to merge 2 commits into
Open
Ttimmahlax wants to merge 2 commits into
Ttimmahlax wants to merge 2 commits into
Conversation
rusty_alloc published 2.2.1 and 2.2.2 while this pull request sat open, so the version it was moving to was no longer the current one. Retargeted in place rather than opened again, so the review history stays put. Still a patch move inside 2.x: the only break in that line was 2.0.0, where default-features = false began selecting no_std, and this takes default features. Co-Authored-By: Claude Opus 5 (1M context) <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
2 participants
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.
Automated dependency rollout by
remade-updater.Moves
rusty_alloc-apito=2.2.0across every repository that declares it, so the portfolio does not end up straddling two versions of one crate.This pull request is one of a set. None of them merge until all of them are green -- a half-merged rollout is the state this tooling exists to prevent.
Generated from the manifests themselves; nothing here is hand-maintained.