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]>

v3.0.1: Release Wasmtime 3.0.1 (#5363)

* Release Wasmtime 3.0.1

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

* Add release notes for 3.0.1

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

v3.0.0: Release Wasmtime 3.0.0 (#5305)

* Release Wasmtime 3.0.0

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

* Update release date

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

v2.0.2: Release Wasmtime 2.0.2 (#5218)

* Release Wasmtime 2.0.2

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

* Add release notes for 2.0.2

* Fix an invalid zero-sized call to mmap

* Fix windows tests

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

v1.0.2: Prepare a Wasmtime 1.0.2 release (#5246)

* Merge pull request from GHSA-wh6w-3828-g9qf

This is a minimal fix for the release branch to fix the issue of having
a memory slot get reused between a module with an image and one without.

* Merge pull request from GHSA-44mr-8vmm-wjhg

This ensures that memories, even with zero contents, still have the
necessary virtual mappings as required by the code generator to report
out-of-bounds reads/writes.

* Merge pull request from GHSA-h84q-m8rr-3v9q

The Rust definition was previously performing a 4-byte write when the C
API was declared as taking an 1-byte buffer.

* CI fixes from CVE patches

* Bump to 1.0.2

* Cherry-pick github actions fixes for 1.0.2 release

Culmination of patches already landed in `main` and `release-2.0.0`

* Release Wasmtime 1.0.2

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

* Fix inst size test for Rust 1.65.0

* Use an alternate doxygen download link (#5150)

* Use an alternate doxygen download link

Looks like doxygen.nl is down otherwise.

* Update link

v2.0.1: Fix the `push-tag` workflow again (#5144)

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

Release Wasmtime 2.0.0

Release Wasmtime 2.0.0 (#5081)

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

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