bump to v0.13.3

AbstractSDK · Jul 5, 2023 · 922a71f · 922a71f
1 parent 458b42a
commit 922a71f
Show file tree

Hide file tree

Showing 6 changed files with 10 additions and 10 deletions.
diff --git a/Cargo.toml b/Cargo.toml
@@ -1,6 +1,6 @@
 [workspace]
 members = ["cw-orch", "packages/*", "contracts/*"]
-version = "0.13.2"
+version = "0.13.3"
 resolver = "2"
 
 [workspace.package]

diff --git a/cw-orch/Cargo.toml b/cw-orch/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "cw-orch"
-version = "0.13.2"
+version = "0.13.3"
 authors = { workspace = true }
 edition = { workspace = true }
 license = { workspace = true }
@@ -55,8 +55,8 @@ eth = ["daemon", "dep:ethers-signers", "dep:ethers-core", "dep:snailquote"]
 
 [dependencies]
 # Default deps
-cw-orch-contract-derive = { path = "../packages/cw-orch-contract-derive", version = "0.13.2" }
-cw-orch-fns-derive = { path = "../packages/cw-orch-fns-derive", version = "0.13.2" }
+cw-orch-contract-derive = { path = "../packages/cw-orch-contract-derive", version = "0.13.3" }
+cw-orch-fns-derive = { path = "../packages/cw-orch-fns-derive", version = "0.13.3" }
 
 cosmwasm-std = { workspace = true }
 cw-multi-test = { workspace = true }

diff --git a/docs/src/quick_start.md b/docs/src/quick_start.md
@@ -8,14 +8,14 @@ To use the `cw-orchestrator`, you need to add `cw-orch` to your contract's TOML
 
 ```shell
 $ cargo add --optional cw-orch
-> Adding cw-orch v0.13.2 to optional dependencies.
+> Adding cw-orch v0.13.3 to optional dependencies.
 ```
 
 Alternatively, you can add it manually in your `Cargo.toml` file as shown below:
 
 ```toml
 [dependencies]
-cw-orch = {version = "0.13.2", optional = true } # Latest version at time of writing
+cw-orch = {version = "0.13.3", optional = true } # Latest version at time of writing
 ```
 
 Now that we have added `cw-orch` as an optional dependency we will want to enable it through a feature. This ensures that the code added by `cw-orch` is not included in the wasm artifact of the contract. To do this add an `interface` feature to the `Cargo.toml` and enable `cw-orch` when it is enabled.

diff --git a/docs/src/single_contract/interfaces.md b/docs/src/single_contract/interfaces.md
@@ -8,14 +8,14 @@ Before we can create an interface we need to add cw-orch to the contract's `Carg
 
 ```shell
 $ cargo add --optional cw-orch
-> Adding cw-orch v0.13.2 to optional dependencies.
+> Adding cw-orch v0.13.3 to optional dependencies.
 ```
 
 or add it manually to the `counter/Cargo.toml` file:
 
 ```toml
 [dependencies]
-cw-orch = {version = "0.13.2", optional = true } # Latest version at time of writing
+cw-orch = {version = "0.13.3", optional = true } # Latest version at time of writing
 ```
 
 We add `cw-orch` as an optional dependency to ensure that it is not included in the wasm artifact of the contract. This way there are no trust assumptions made about the code added by `cw-orch`, making it safe to use for production contracts.

diff --git a/packages/cw-orch-contract-derive/Cargo.toml b/packages/cw-orch-contract-derive/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "cw-orch-contract-derive"
-version = "0.13.2"
+version = "0.13.3"
 authors = { workspace = true }
 edition = { workspace = true }
 license = { workspace = true }

diff --git a/packages/cw-orch-fns-derive/Cargo.toml b/packages/cw-orch-fns-derive/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "cw-orch-fns-derive"
-version = "0.13.2"
+version = "0.13.3"
 authors = { workspace = true }
 edition = { workspace = true }
 license = { workspace = true }