Skip to content

chore: rusty_alloc-api -> =2.2.0 - #9

Open
Ttimmahlax wants to merge 2 commits into
mainfrom
chore/rusty_alloc-2.2.0
Open

Ttimmahlax wants to merge 2 commits into
mainfrom
chore/rusty_alloc-2.2.0

Conversation

@Ttimmahlax

Copy link
Copy Markdown
Contributor

The wave planner could not order this repository — it sits in the rusty_time/mata-master publish cycle — but 2.2.0 is already on crates.io, so no publish has to happen first and the bump stands on its own.

The only break in the 2.x line was 2.0.0, where default-features = false began selecting no_std. This takes the allocator on default features, so it is unaffected.

Verified: cargo check --workspace clean.

🤖 Generated with Claude Code

tim-almond-house and others added 2 commits September 19, 2026 22:45
The wave planner could not order this repository -- it sits in the
rusty_time/mata-master publish cycle -- but 2.2.0 is already on crates.io, so
no publish has to happen first and the bump stands on its own.

The only break in the 2.x line was 2.0.0, where `default-features = false`
began selecting `no_std`. This takes the allocator on default features, so it
is unaffected.

Verified: cargo check --workspace clean.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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>
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