You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff 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.
* 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.
0 commit comments