v0.5.0

⚠️ Breaking changes ⚠️

• WIT files now require semicolons at the end of most lines.

Compatibility

• Wasmtime: 15.0.0
• Warg (registry support): 0.2.0

What's Changed

• Update README installation instructions. by @peterhuene in #169
• Update wasm-tools dependencies by @alexcrichton in #176
• Add upgrade subcommand by @jeffparsons in #175
• Better error message when deserializing RegistryPackage by @rylev in #180
• Suppress dead code warnings in bindings. by @peterhuene in #182
• Ensure CI runs on release branches. by @peterhuene in #184
• Add semicolons to WIT. by @peterhuene in #185
• Merge release-0.4.0 to main. by @peterhuene in #186
• Update crate dependencies. by @peterhuene in #190
• Fix bindings version warning and upgrade command. by @peterhuene in #187
• Update README instructions by @nated0g in #193
• Bump version to 0.5.0 by @peterhuene in #195

New Contributors

• @nated0g made their first contribution in #193

Full Changelog: v0.4.0...v0.5.0

v0.4.1

Compatibility

• Wasmtime: 14.0.0
• Warg (registry support): 0.2.0

What's Changed

This release contains a fix for unused code warnings come from bindings, usually as a result of having unused imported functions.

• Cherry pick fix for 0.4.1 release. by @peterhuene in #183

Full Changelog: v0.4.0...v0.4.1

v0.4.0

⚠️ Breaking changes ⚠️

Mismatched crate versions

This release of cargo-component contains a breaking change that will lead to build errors if you build a component that uses a mismatched version of the cargo-component-bindings crate.

If cargo-component detects a mismatched version, it will print a warning for each manifest in your workspace with an incompatible version.

To correct the issue, please update the version of the cargo-component-bindings dependency in your Cargo.toml to 0.4.0.

We plan to introduce a cargo-component subcommand to automate upgrades in the future.

Arguments to cargo_component_bindings::generate!

If you are currently passing arguments to the cargo_component_bindings::generate! macro, the macro no longer accepts arguments and will error if arguments are passed.

To correct this issue, please move any arguments to the [package.metadata.component.bindings] table in your Cargo.toml.

The supported settings are:

• implementor: The name of the type to implement world exports on.
• resources: A map of resource names to resource implementor types.
• ownership: The ownership model to use for generated types.
• derives: Additional derive macro attributes to add to generated types.

Compatibility

• Wasmtime: 14.0.0
• Warg (registry support): 0.2.0

What's Changed

This release contains improvements to component build times by reducing the number of dependencies required to build a component.

Additionally, rust-anzlyzer support is fixed, so changes to local WIT files should now be reflected when rust-analyzer re-parses Rust source code (i.e. on save of an .rs file or after a cargo component invocation).

The "go to definition" functionality provided by rust-analyzer now works with bindings types as we now generate a source file for the definitions rather than relying on a macro expansion.

The prebuilt artifacts associated with the release are now much smaller.

• Reduce the size of published artifacts. by @peterhuene in #166
• Refactor bindings generation. by @peterhuene in #167
• Bump cargo-component version to 0.4.0. by @peterhuene in #168

Full Changelog: v0.3.1...v0.4.0

v0.3.1

Compatibility

• Wasmtime: 14.0.0
• Warg (registry support): 0.2.0

What's Changed

• chore: publish binaries by @morenol in #161
• fix: windows build should use bash by @morenol in #163
• Fix bindings generation for exports of versioned interfaces. by @peterhuene in #164
• Bump patch version. by @peterhuene in #165

Full Changelog: v0.3.0...v0.3.1

dev: chore: publish binaries (#161)

Published artifacts from the latest build

v0.3.0

Compatibility

• Wasmtime: 14.0.0
• Warg (registry support): 0.2.0

What's Changed

• feat(macro): Adds custom derive attributes by @thomastaylor312 in #150
• build: update dependencies by @morenol in #156
• Update dependencies to latest versions. by @peterhuene in #157
• Bump cargo-component to 0.3.0. by @peterhuene in #158

New Contributors

• @thomastaylor312 made their first contribution in #150
• @morenol made their first contribution in #156

Full Changelog: v0.2.0...v0.3.0

v0.2.0

Compatibility

• Wasmtime: 13.0.0
• Warg (registry support): 0.1.0

What's Changed

This is the first release of cargo-component and the wit tool.

cargo-component

Released as version 0.2.0 and is compatible with the WASI interfaces supported by Wasmtime 13.

Note: cargo-component accidentally used version 0.1.0 as a placeholder release to squat the crate name; that version is non-functional.

wit

Released as version 0.1.0.

Both tools support warg registries with client version 0.1.0.

Full Changelog: https://github.com/bytecodealliance/cargo-component/commits/v0.2.0