10 curated breaking changes across major versions of windows-implement. Use this as a migration checklist before bumping dependencies.
The [windows-metadata](https://crates.io/crates/windows-metadata) crate is a low-level metadata library for ECMA-335, providing both a reader and writer for the ECMA-335 metadata format (#3560) used by .NET, WinRT, and more recently the Win32 metadata. It is technically a brand new implementation but reuses the older crate name from my first attempt at a metadata parser in Rust. The emphasis is on low-level. While it is easy to use, the metadata format is intended for tools to use internally. Th
The [windows-bindgen](https://crates.io/crates/windows-bindgen) crate provides a number of improvements including new diagnostics (#3498), streamlined and more capable reference support (#3497, #3492), hardened method overloading (#3477), far fewer `transmute` calls, as well as many other critical fixes and improvements.
The [windows-core](https://crates.io/crates/windows-core) crate is largely unchanged but required some breaking changes to support `windows-bindgen` type system improvements.
The [windows-registry](https://crates.io/crates/windows-registry) crate continues to improve with generalized support for access rights (#3482), open options (#3461), and other minor improvements.
The [windows](https://crates.io/crates/windows) crate now delegates to the `windows-numerics`, `windows-future`, and `windows-collections` crates for those types, as well as a number of critical fixes and improvements to features and `cfg` guards (#3431), and many other small improvements.
`windows-core` 0.59.0
`windows-implement` 0.59.0
`windows-interface` 0.59.0
`windows-targets` 0.53.0
`windows_i686_msvc` 0.53.0
Get this data programmatically \u2014 free, no authentication.
curl https://depscope.dev/api/breaking/cargo/windows-implement