chore: allocator to =2.2.0, and s3zstd is not a registry crate - #21
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-api =2.0.5 -> =2.2.0 crates/rzstd-alloc
rusty_alloc =2.0.5 -> =2.2.0 bare-metal/esp32s3
rusty_alloc-api =2.0.5 -> =2.2.0 bare-metal/esp32s3
Within 2.x, so nothing here changes shape. The only break in the 2.x line was
2.0.0 -- `default-features = false` now selects `no_std` -- and its changelog
records that consumers on default features are unaffected. 2.1.0 and 2.2.0
carry no API change at all.
This also closes part of a three-way split on the allocator across the
portfolio: mata-master sits on =1.1.6, this repo was on =2.0.5, and 2.2.0 is
what is published.
`s3zstd` gets `publish = false`. It is firmware for an ESP32-S3 devkit and has
never been on crates.io. Being outside the workspace already put it beyond
release-plz's reach, but nothing said so in the manifest, so the portfolio
tooling counted it among the crates this repository publishes.
Verified: `cargo check --workspace --all-targets --features profile` is clean.
Without `--features profile` the bench examples fail to compile -- that is
pre-existing and by design (the examples are gated behind it), and it fails
identically on origin/main with this change stashed.
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>
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.
rusty_alloc-api(crates/rzstd-alloc)=2.0.5=2.2.0rusty_alloc(bare-metal/esp32s3)=2.0.5=2.2.0rusty_alloc-api(bare-metal/esp32s3)=2.0.5=2.2.0Within 2.x, so nothing changes shape. The only break in the 2.x line was 2.0.0 —
default-features = falsenow selectsno_std— and its changelog records that consumers on default features are unaffected. 2.1.0 and 2.2.0 carry no API change.This closes part of a three-way split across the portfolio:
mata-mastersits on=1.1.6, this repo was on=2.0.5, and 2.2.0 is what is published.s3zstdgetspublish = falseIt is firmware for an ESP32-S3 devkit and has never been on crates.io. Being outside the workspace already put it beyond release-plz's reach, but nothing said so in the manifest — so the portfolio tooling counted it among the crates this repository publishes.
Verification
cargo check --workspace --all-targets --features profileis clean. Without--features profilethe bench examples fail to compile; that is pre-existing and by design (they are gated behind it), and it fails identically onorigin/mainwith this change stashed.🤖 Generated with Claude Code