Repository navigation
bump rusty_alloc-api to =2.2.6 - #11
Merged
Merged
Conversation
The rollout edits the manifest through the API; CI builds with --locked, so the lockfile has to move with it. Wave 1 of the portfolio release campaign. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rusty_rtos_alloc asserts the re-exported rusty_alloc-api VERSION so a bump is never silent. Wave 1 of the portfolio release campaign moves the pin to =2.2.6 (one fix: a merged free span keeps its neighbour's purged flag), so the guard moves with it and records why. Co-Authored-By: Claude Opus 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
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.6across 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.