Merge pull request #1781 from polywrap/origin-dev

Prep 0.10.4

Author: dOrgJelli

.github/workflows/cd-containers.yaml

@@ -11,7 +11,7 @@ jobs:
       github.event.pull_request.merged &&
       endsWith(github.event.pull_request.title, '/workflows/cd-containers') &&
       github.event.pull_request.user.login != 'polywrap-build-bot'
-    runs-on: ubuntu-20.04
+    runs-on: ubuntu-latest
     steps:
       - name: Checkout
         uses: actions/checkout@v3

.github/workflows/ci-containers.yaml

@@ -0,0 +1,32 @@
+name: CI-Containers
+
+on:
+  pull_request:
+    paths:
+      - "packages/cli/src/lib/defaults/build-strategies/wasm/rust/vm/Dockerfile"
+      - "packages/cli/src/lib/defaults/build-strategies/wasm/assemblyscript/vm/Dockerfile"
+
+jobs:
+  Build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v2
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v2
+
+      - name: Cache Image Directories
+        run: |
+          echo IMAGE_RS_VM_DIR=./packages/cli/src/lib/defaults/build-strategies/wasm/rust/vm >> $GITHUB_ENV
+          echo IMAGE_AS_VM_DIR=./packages/cli/src/lib/defaults/build-strategies/wasm/assemblyscript/vm >> $GITHUB_ENV
+
+      - name: Build RS VM Image
+        working-directory: ${{env.IMAGE_RS_VM_DIR}}
+        run: |
+          docker buildx build . --platform=linux/amd64,linux/arm64
+
+      - name: Build AS VM Image
+        working-directory: ${{env.IMAGE_AS_VM_DIR}}
+        run: |
+          docker buildx build . --platform=linux/amd64,linux/arm64

CHANGELOG.md

@@ -1,3 +1,21 @@
+# Polywrap Origin (0.10.4)
+## Features
+**`polywrap` CLI:**
+* [PR-1735](https://github.com/polywrap/cli/pull/1735) **Add Docs Manifest & `polywrap docs init` Command**
+  * The `polywrap.docs.yaml` manifest is used to add additional metadata to your wraps.
+* [PR-1776](https://github.com/polywrap/cli/pull/1776) **Add HTTP Headers To HTTP Deploy Module**
+  * The `http` deploy module now supports the `headers` configuration property.
+
+## Bugs
+**`polywrap` CLI:**
+* [PR-1773](https://github.com/polywrap/cli/pull/1773) **Don't Install `wasm-opt` Every `local` Rust Build**
+  * The `local` strategy for rust wasm projects was unexpectedly installing `wasm-opt` every time it was run, leading to very long build times.
+
+**`@polywrap/schema-bind`:**
+* [PR-1775](https://github.com/polywrap/cli/pull/1775) **Fix Python Plugin Bindings**
+  * The wrap abi type `Bytes` can now be properly used within rust plugins.
+* [PR-1753](https://github.com/polywrap/cli/pull/1753) **Fix Python Plugin Bindings**
+
 # Polywrap Origin (0.10.3)
 ## Features
 **`polywrap` CLI:**

CONTRIBUTING.md

@@ -0,0 +1,28 @@
+# Contributing
+Thank you for considering contributing to the Polywrap CLI! We welcome contributions from the community to help improve and enhance the project. Look through this repository's [issues](https://github.com/polywrap/cli/issues) to see what we're focused on solving.
+
+## Pre-Requisites
+To be able to fully build and test all functionality within the CLI, you'll need the following programs installed:  
+`nvm`  
+`node`  
+`yarn`  
+`docker`  
+`docker-compose`  
+`cue`  
+
+## Installation
+
+From the root directory, run `nvm install && nvm use` to install the correct version of Node.JS. Next, run `yarn` to install all dependencies for all packages.
+
+## Build
+
+Running `yarn build` from the root directory will build all packages. After this, if you'd like to rebuild an individual package you're making changes to, simply run `yarn build` within the specific `./packages/...` folder you're working in.
+
+## Testing
+
+Run `yarn test` from the root to test everything, and `yarn test` within a specific package folder to test just that package.
+
+## Feedback and Discussions
+For questions, suggestions, or discussions, open an issue or create a discussion within the [Polywrap Discord](https://discord.polywrap.io).
+
+Happy coding!

DEV_GUIDELINES.md

@@ -1,82 +1,17 @@
-![Public Release Announcement](https://user-images.githubusercontent.com/5522128/177473887-2689cf25-7937-4620-8ca5-17620729a65d.png)
+![polywrap-banner](https://raw.githubusercontent.com/polywrap/branding/master/assets/banner.png)
 
-[**Polywrap**](https://polywrap.io/) is a developer tool that enables easy integration of Web3 protocols into any application. It makes it possible for applications on any platform, written in any language, to read and write data to Web3 protocols.
+**Polywrap** is a framework for developing software powered by Wraps. Wraps are software modules that are:
+* **Portable** - run in any environment
+* **Composable** - easily and safely call into one another
 
-# Getting Started
+We believe that the future of software will be driven by a multitude of highly-specialized, platform-agnostic modules rather than monoliths.
 
-Have questions or want to get involved? Join our community [Discord](https://discord.polywrap.io) or [open an issue](https://github.com/polywrap/monorepo/issues) on Github.
+## Getting Started
 
-For detailed information about Polywrap and the WRAP standard, visit our [developer documentation](https://docs.polywrap.io/).
+To get started using the Polywrap CLI, follow the [installation instructions](./packages/cli//README.md#installation).
 
-# Contributing
+If you haven't already, checkout Polywrap's [developer documentation](https://docs.polywrap.io), where you'll find quick-starts & in-depth tutorials to help you accomplish your goals.
 
-The Polywrap project is completely open-source and we welcome contributors of all levels.
-
-Come visit our [Github issues](https://github.com/polywrap/monorepo/issues) to see the problems we're focused on solving. Here are some of our tags for issues and what they mean:
-
-- `good first issue` - These are good first issues for newcomers to learn about how our project works
-
-- `pri-0`, `pri-1` and `pri-2` - These are our priority issues, with `pri-0` being our highest priority and `pri-2` being lower.
-
-- `alpha-blocker` - We're in pre-alpha right now and to get to alpha, we need to resolve all alpha blocker issues
-
-- `beta-blocker` - After our alpha release, we'll start working towards releasing our beta! These are the blockers for us in reaching that milestone.
-
-Below are a series of steps to get started with our monorepo after you've cloned it into your local repository.
-
-Before contributing to this repository, please read the [developer guidelines](DEV_GUIDELINES.md).
-
-## Pre-reqs
-
-You'll need the following installed before building your wrapper:
-
-`nvm`
-
-`yarn`
-
-`docker`
-
-`docker-compose`
-
-## Installation
-
-To ensure all of your project's dependencies are installed, from inside your project's directory, simply run:
-
-```
-nvm install && nvm use
-yarn
-```
-
-## Build
-
-Run the following to compile the monorepo:
-
-`yarn build`
-
-## Test
-
-Run the following to test if the build worked:
-
-```
-yarn test
-```
-
-## Lint
-
-To lint your project directory, run the following:
-
-```
-yarn lint
-```
-
-To auto-fix lint errors:
-
-```
-yarn lint:fix
-```
-
-# Resources
-- [Website](https://polywrap.io/)
-- [Documentation](https://docs.polywrap.io/)
-- [Forum](https://forum.polywrap.io/)
+## Contributing
 
+If you're interested in contributing to this, or any Polywrap repository, checkout the [contributing guide](./CONTRIBUTING.md) as well as [join our Discord](https://discord.polywrap.io)!

README.md

@@ -1 +1 @@
-0.10.3
+0.10.4

VERSION

@@ -14,7 +14,7 @@
   "commands_build_keypressListener_exit": "Exit: [CTRL + C], [ESC], or [Q]",
   "commands_build_keypressListener_watching": "Watching",
   "commands_build_options_h": "Show usage information",
-  "commands_build_options_m": "Path to the Polywrap Build manifest file (default: {default})",
+  "commands_build_options_m": "Path to the Polywrap manifest file (default: {default})",
   "commands_build_options_o": "Output directory for build results (default: {default})",
   "commands_build_options_o_path": "path",
   "commands_build_options_options": "options",
@@ -194,6 +194,13 @@
   "commands_manifest_formatError": "Unsupported manifest format. Please make sure that you have the 'format' field present in {fileName} with one of the following values: {values}",
   "commands_manifest_migrate_targetFormatError": "Unsupported target format. Supported formats: {formats}",
   "commands_manifest_projectTypeError": "Unsupported project type.",
+  "commands_docs_description": "Documentation commands",
+  "commands_docs_init_description": "Initialize wrap docs",
+  "commands_docs_init_m_path": "path",
+  "commands_docs_options_m": "Path to the Polywrap manifest file (default: {default})",
+  "commands_docs_init_error_manifest_exists": "The {manifestFile} manifest already exists.",
+  "commands_docs_init_warn_update_manifest": "Set the 'extensions.docs' property to {docsManifestFile} within your project's root manifest at {manifestFile}",
+  "commands_docs_init_msg_manifest_created": "Written docs manifest to {manifestFile}",
   "lib_codeGenerator_genCodeError": "Failed to generate types",
   "lib_codeGenerator_genCodeText": "Generate types",
   "lib_codeGenerator_genCodeWarning": "Warnings while generating types",

packages/cli/lang/en.json

@@ -14,7 +14,7 @@
   "commands_build_keypressListener_exit": "Exit: [CTRL + C], [ESC], or [Q]",
   "commands_build_keypressListener_watching": "Watching",
   "commands_build_options_h": "Show usage information",
-  "commands_build_options_m": "Path to the Polywrap Build manifest file (default: {default})",
+  "commands_build_options_m": "Path to the Polywrap manifest file (default: {default})",
   "commands_build_options_o": "Output directory for build results (default: {default})",
   "commands_build_options_o_path": "path",
   "commands_build_options_options": "options",
@@ -116,11 +116,11 @@
   "commands_create_error_badUrl": "URL {url} uses an invalid format. Valid URL formats: {formats}",
   "commands_create_options_command": "command",
   "commands_create_options_commands": "Commands",
-  "commands_create_options_createApp": "Create a Polywrap application",
-  "commands_create_options_createPlugin": "Create a Polywrap plugin",
-  "commands_create_options_createProject": "Create a Polywrap wasm wrapper",
+  "commands_create_options_createApp": "Create a Polywrap application.",
+  "commands_create_options_createPlugin": "Create a Polywrap plugin.",
+  "commands_create_options_createProject": "Create a Polywrap wasm wrapper.",
   "commands_create_options_h": "Show usage information",
-  "commands_create_options_t": "Download template from a .git URL",
+  "commands_create_options_t": "Download template from a URL.",
   "commands_create_options_t_url": "URL",
   "commands_create_options_formats": "formats",
   "commands_create_options_lang": "lang",
@@ -194,6 +194,13 @@
   "commands_manifest_formatError": "Unsupported manifest format. Please make sure that you have the 'format' field present in {fileName} with one of the following values: {values}",
   "commands_manifest_migrate_targetFormatError": "Unsupported target format. Supported formats: {formats}",
   "commands_manifest_projectTypeError": "Unsupported project type.",
+  "commands_docs_description": "Documentation commands",
+  "commands_docs_init_description": "Initialize wrap docs",
+  "commands_docs_init_m_path": "path",
+  "commands_docs_options_m": "Path to the Polywrap manifest file (default: {default})",
+  "commands_docs_init_error_manifest_exists": "The {manifestFile} manifest already exists.",
+  "commands_docs_init_warn_update_manifest": "Set the 'extensions.docs' property to {docsManifestFile} within your project's root manifest at {manifestFile}",
+  "commands_docs_init_msg_manifest_created": "Written docs manifest to {manifestFile}",
   "lib_codeGenerator_genCodeError": "Failed to generate types",
   "lib_codeGenerator_genCodeText": "Generate types",
   "lib_codeGenerator_genCodeWarning": "Warnings while generating types",

packages/cli/lang/es.json

@@ -4,7 +4,7 @@ import { GetPathToCliTestFiles } from "@polywrap/test-cases";
 import fs from "fs";
 import path from "path";
 
-jest.setTimeout(1200000);
+jest.setTimeout(1500000);
 
 describe("e2e tests for build command", () => {
   const testCaseRoot = path.join(GetPathToCliTestFiles(), "build-cmd/wasm/rust");