Skip to content

chore: rusty_alloc/-api =2.2.0 -> =2.2.2 across the eight seams - #44

Open
Ttimmahlax wants to merge 1 commit into
masterfrom
chore/rusty_alloc-2.2.2
Open

Ttimmahlax wants to merge 1 commit into
masterfrom
chore/rusty_alloc-2.2.2

Conversation

@Ttimmahlax

Copy link
Copy Markdown
Collaborator

FFAI brought itself to =2.2.0 after the portfolio allocator rollout ran, so it was never in that wave — and 2.2.1 and 2.2.2 have published since. Eight manifests, all patch moves inside 2.x.

The only break in the 2.x line was 2.0.0, where default-features = false began selecting no_std. Every one of these takes the allocator on default features, so none is affected.

Verified: cargo check -p ffai-core clean; the whole workspace resolves.

🤖 Generated with Claude Code

FFAI brought itself to =2.2.0 after the portfolio allocator rollout ran, so
it was never in that wave -- and 2.2.1 and 2.2.2 have published since. Eight
manifests, all patch moves inside 2.x.

The only break in the 2.x line was 2.0.0, where `default-features = false`
began selecting `no_std`. Every one of these takes the allocator on default
features, so none is affected.

Verified: `cargo check -p ffai-core` clean, and the whole workspace resolves.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants