NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io · #681 most downloaded on crates.io
derive proc-macros for `bytemuck`
Last release 26 days ago
11 Sep 2026
Release timing varies
gaps range from 8 days to 9 months
Some releases are documented
notes for 13 of 25 stable releases
1 version withdrawn
withdrawn after publishing
6 years old
28 releases · first in 2020
One column per quarter.
chore: Release bytemuck_derive version 1.12.1
chore: Release bytemuck_derive version 1.12.1
bytemuck_derive version because of a regression in
how it handled align(N) attributes.chore: Release bytemuck_derive version 1.12.0
chore: Release bytemuck_derive version 1.12.0
chore: Release bytemuck_derive version 1.11.0
chore: Release bytemuck_derive version 1.11.0
chore: Release bytemuck_derive version 1.10.2
chore: Release bytemuck_derive version 1.10.2
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Bumped the minimum bytemuck_derive dependency version from 1.0 to 1.1. The fact that bytemuck and bytemuck_derive are separate crates at all is an unf
bytemuck_derive dependency version from 1.0 to 1.1.
The fact that bytemuck and bytemuck_derive are separate crates at all is
an unfortunate technical limit of current Rust, woe and calamity.fu5ha added the NoUninit, AnyBitPattern, and CheckedBitPattern traits. This allows for a more fine-grained level of detail in what casting operations
NoUninit, AnyBitPattern, and
CheckedBitPattern traits. This allows for a more fine-grained level of
detail in what casting operations are allowed for a type. Types that already
implement Zeroable and Pod will have a blanket impl for these new traits.
This is a "preview" of the direction that the crate will probably go in the
eventual 2.0 version. We're still waiting on Project Safe
Transmute for an actual
2.0 version of the crate, but until then please enjoy this preview.union types in the derive macros. I
still don't know how any of the proc-macro stuff works at all, so please
direct questions to her.Nothing published for this version
try_pod_read_unaligned and pod_read_unaligned let you go from &[u8] to T:Pod without worrying about alignment.
try_pod_read_unaligned and pod_read_unaligned let you go from &[u8] to
T:Pod without worrying about alignment.Soundness Fix: The wrap/peel methods for owned value conversion, added to TransparentWrapper in 1.6, can cause a double-drop if used with types that i
TransparentWrapper in 1.6, can cause a double-drop if used with types that
impl Drop. The fix was simply to add a ManuallyDrop layer around the value
before doing the transmute_copy that is used to wrap/peel. While this fix
could technically be backported to the 1.6 series, since 1.7 is semver
compatible anyway the 1.6 series has simply been yanked.Nothing published for this version
DJMcNab did a fix so that the crate can build for SPIR-V PR 67
Nothing published for this version
Nothing published for this version
thomcc fixed up the CI and patched over a soundness hole in offset_of!. PR 38
Nothing published for this version
Had a bug because the CI was messed up! It wasn't soundness related, because it prevented the crate from building entirely if the extern_crate_alloc f
extern_crate_alloc
feature was used. Still, this is yanked, sorry.Nothing published for this version
A fully sound offset_of! macro #10
offset_of! macro
#10Contiguous trait for when you've got enums with declared values
all in a row #12TransparentWrapper marker trait for when you want to more clearly
enable adding and removing a wrapper struct to its inner value
#15Nothing published for this version
SimonSapin added from_bytes, from_bytes_mut, try_from_bytes, and try_from_bytes_mut (PR Link)
from_bytes,
from_bytes_mut, try_from_bytes, and try_from_bytes_mut (PR
Link)Added much more proper documentation.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →