Skip to content

Commit 575a5a5

Browse files
committed
chore: prep 0.10.1
1 parent a40d775 commit 575a5a5

2 files changed

Lines changed: 21 additions & 1 deletion

File tree

CHANGELOG.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,23 @@
1+
# Polywrap Origin (0.10.1)
2+
## Features
3+
**`@polywrap/wasm-js`:**
4+
* [PR-3](https://github.com/polywrap/javascript-client/pull/3) **WasmWrapper Subinvcations Now Retain The Resolution Context**
5+
* Added `resolutionContext` to the `WasmWrapper`'s state.
6+
* Pass the `resolutionContext` through to all subinvocations.
7+
8+
## Bugs
9+
**`@polywrap/client-config-builder-js`**
10+
* [PR-8](https://github.com/polywrap/javascript-client/pull/8) **`tryResolveUri` Now Returns Wrap Packages**
11+
* The default resolver should not automatically convert packages to wrappers. Based on this, the `PackageToWrapperResolver` has been removed from the default config bundle.
12+
13+
**`@polywrap/core-client-js`:**
14+
* [PR-3](https://github.com/polywrap/javascript-client/pull/3) **Properly Track Subinvocation Resolution Contexts**
15+
* Instead of passing the core resolution context to the resolution and invocation processes, seperate sub contexts are created for them. This means that subinvokes will now be tracked in the resolution context.
16+
17+
**`@polywrap/plugin-js`:**
18+
* [PR-3](https://github.com/polywrap/javascript-client/pull/3) **Properly Track Subinvocation Resolution Contexts**
19+
* The client instance provided to plugin methods has been wrapped, enabling the automatic tracking of all subinvocation resolution contexts.
20+
121
# Polywrap Origin (0.10.0)
222
## Features
323
**`@polywrap/client-js`:**

VERSION

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
0.10.0
1+
0.10.1

0 commit comments

Comments
 (0)