chore(main): release wasmer-sdk 0.6.0 #375
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.6.0 (2023-12-21)
⚠ BREAKING CHANGES
@wasmer/sdk
Runtime
has removed the limit on the maximum number of worker threads it is allowed to spawn. The correspondingpoolSize
option has been removed fromRuntimeOptions
.package.json
so importing@wasmer/sdk
will pull in the version withwasmer_js_bg.wasm
embedded as a base64 string, by defaultFeatures
@wasmer/sdk
Runtime
has removed the limit on the maximum number of worker threads it is allowed to spawn. The correspondingpoolSize
option has been removed fromRuntimeOptions
. (d5da4ea)Bug Fixes
wasmer
dependency to pick up wasmerio/wasmer#4366 (c3c5a5d)package.json
so importing@wasmer/sdk
will pull in the version withwasmer_js_bg.wasm
embedded as a base64 string, by default (0c850a5)This PR was generated with Release Please. See documentation.