Merged
Conversation
Merged
|
GitHub Release Published |
|
Crates.io Release Published |
|
NPM Release Published |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Polywrap Origin (0.9.0)
Features
polywrapCLI: Console logging has been improved, and all commands now support-q, --quietand-v, --verboseoptions.polywrapCLI: Build times are faster for wasm wrappers!!! Thebuildcommand has been updated to include the concept of "build strategies". The existing way of building (viaDockerfileimage layers) is available through thepolywrap build --strategy imagecommand. Building without Docker (if all build-time dependencies are installed locally) can be performed using--strategy local. And lastly, the new default build strategy is--strategy vm, which runs all build steps in a pre-built base image, allowing for near-local speeds (once the image has been downloaded).--strategy imageis useful for source-code verification, something we'll be better supporting in the future.@polywrap/schema-bind:wasm/rustnow has support forprintln!(...)andprint!(...)macros. They have been redefined to use thepolywrap_wasm_rs::wrap_debug_log(...)function.@polywrap/client-js:PolywrapClient.invoke(...)now supports invoke-time environment variables, passed in via theenvproperty.polywrapCLI: Themanifestcommand has been added:--formatoption to themigratecommand, enabling the targeting of specific format versions when migrating manifests (ex:polywrap manifest migrate -f 0.2.0).polywrapCLI,@polywrap/tracing-js: Thetracinginfrastructure module (i.e.polywrap infra up --modules tracing) now uses version0.11.0of theSizNoztracing service. Additionally the underlying@polywrap/tracing-jslibrary has been updated to support this, and also now has named traces via thetraceNameconfiguration property.Bugs
polywrapCLI: Generated build files from thevmstrategy now have proper file-system permissions.@polywrap/ipfs-plugin-js: Fallback providers are now properly being used.polywrapCLI: Thepolywrap.app.yamlandpolywrap.plugin.yamlproject manifest file names are being deprecated in favor of a unifiedpolywrap.yamlfile for all types of projects (wasm, interface, plugin, app). They will still silently work now, but in the future will no longer be recognized defaults.@polywrap/core-js: TheUriclass now properly formats itself when beingJSON.stringify(...)'d.@polywrap/core-js: Correctly handle errors in thegetImplementationsalgorithm.@polywrap/ipfs-plugin-js,@polywrap/ipfs-resolver-plugin-js: Remove the use ofrequire(...)statements.@polywrap/polywrap-manifest-types-js: Manifest migration logic has been upgraded to use a strategy that finds a "shortest path" between thefromandtoformat versions, using predefined migration functions.Breaking Changes
@polywrap/core-js:Wrapper.getFile(...)andWrapper.getManifest(...)no longer require aClientinstance as a second function argument.@polywrap/core-js,@polywrap/client-js: AllClientConfigproperties are nowreadonly.@polywrap/core-js:executeMaybeAsyncFunctionhas been removed.@polywrap/client-js: The following methods now return theResult<T, E>type, and will not throw exceptions:getManifest(...),getFile(...),getImplementations(...),query(...),invokeWrapper(...),invoke(...),loadWrapper(...).@polywrap/client-js:PolywrapClient.invoke(...)no longer accepts invoke-time reconfiguration via theconfigproperty. Users who wish to reconfigure the client can do so by callingclient.getConfig(), modifying it via theClientConfigBuilder, and constructing a newPolywrapClientinstance.