v7.0.1: Release Wasmtime 7.0.1 (#6275)

* Release Wasmtime 7.0.1

[automatically-tag-and-release-this-commit]

* Update mio to build on Rust 1.69

* Add missed Cargo.lock update, update deny metadata

Metadata for `cargo deny` is copied from the `main` branch

---------

Co-authored-by: Wasmtime Publish <[email protected]>
Co-authored-by: Alex Crichton <[email protected]>

v6.0.2: Release Wasmtime 6.0.2 (#6274)

* Release Wasmtime 6.0.2

[automatically-tag-and-release-this-commit]

* Update mio to build on Rust 1.69

---------

Co-authored-by: Wasmtime Publish <[email protected]>
Co-authored-by: Alex Crichton <[email protected]>

v8.0.0: Release Wasmtime 8.0.0 (#6249)

[automatically-tag-and-release-this-commit]

Co-authored-by: Wasmtime Publish <[email protected]>

v7.0.0: Release Wasmtime 7.0.0 (#6065)

* Release Wasmtime 7.0.0

[automatically-tag-and-release-this-commit]

* Revert back submodule

---------

Co-authored-by: Wasmtime Publish <[email protected]>
Co-authored-by: Alex Crichton <[email protected]>

v6.0.1: Release Wasmtime 6.0.1 (#5939)

[automatically-tag-and-release-this-commit]

Co-authored-by: Wasmtime Publish <[email protected]>

v5.0.1: Release Wasmtime 5.0.1 (#5937)

[automatically-tag-and-release-this-commit]

Co-authored-by: Wasmtime Publish <[email protected]>

v4.0.1: Release Wasmtime 4.0.1 (#5938)

[automatically-tag-and-release-this-commit]

Co-authored-by: Wasmtime Publish <[email protected]>

v6.0.0: Release Wasmtime 6.0.0 (#5837)

[automatically-tag-and-release-this-commit]

Co-authored-by: Wasmtime Publish <[email protected]>

v5.0.0: Release Wasmtime 5.0.0 (#5602)

* Release Wasmtime 5.0.0

[automatically-tag-and-release-this-commit]

* Update release notes for 5.0.0 (#5539)

* Fix a debug assert with `wasm_backtrace(false)` (#5580)

This commit fixes an issue where when backtraces were disabled but a
host function returned an error it would trigger a debug assertion
within Wasmtime. The fix here is to update the condition of the debug
assertion and add a test doing this behavior to ensure it works in the
future.

I've also further taken the liberty in this commit to remove the
deprecation notice for `Config::wasm_backtrace`. We don't really have a
strong reason for removing this functionality at this time and users
have multiple times now reported issues with performance that seem
worthwhile to keep the option. The latest issue, #5577, has a use case
where it appears the quadratic behavior is back in a way that Wasmtime
won't be able to detect. Namely with lots of wasm interleaved with host
on the stack if the original error isn't threaded through the entire
time then each host error will trigger a new backtrace since it doesn't
see a prior backtrace in the error being returned.

While this could otherwise be fixed with only capturing one contiguous
backtrace perhaps this seems reasonable enough to leave the
`wasm_backtrace` config option for now.

Closes #5577

* Add component model wasmtime feature to Docs.rs (#5558)

Co-authored-by: Wasmtime Publish <[email protected]>
Co-authored-by: Alex Crichton <[email protected]>
Co-authored-by: Kyle Brown <[email protected]>

v4.0.0: Release Wasmtime 4.0.0 (#5478)

[automatically-tag-and-release-this-commit]

Co-authored-by: Wasmtime Publish <[email protected]>