Release 111 updates

gear-foundation · AndrePanin · Mar 4, 2024 · Mar 4, 2024 · Mar 4, 2024 · deea4e4fdb99129e41a5583552020e9c05a740ac
commit deea4e4fdb99129e41a5583552020e9c05a740ac
diff --git a/docs/developing-contracts/gstd.md b/docs/developing-contracts/gstd.md
@@ -123,7 +123,7 @@ The `debug!` macro is available only when the `"debug"` feature is enabled for t
 
 ```toml
 [dependencies]
-gstd = { git = "https://github.com/gear-tech/gear.git", tag = "v1.0.2", features = ["debug"] }
+gstd = { git = "https://github.com/gear-tech/gear.git", tag = "v1.1.1", features = ["debug"] }
 ```
 
 :::
diff --git a/docs/developing-contracts/introduction.md b/docs/developing-contracts/introduction.md
@@ -93,7 +93,7 @@ Add it to the `[build-dependencies]` section in the `Cargo.toml` file:
 
 ```toml
 [build-dependencies]
-gear-wasm-builder = { git = "https://github.com/gear-tech/gear.git", tag = "v1.0.2", features = ["wasm-opt"] }
+gear-wasm-builder = { git = "https://github.com/gear-tech/gear.git", tag = "v1.1.1", features = ["wasm-opt"] }
 ```
 
 And add the following code to the `build.rs` file:

diff --git a/docs/developing-contracts/testing-gclient.mdx b/docs/developing-contracts/testing-gclient.mdx
@@ -26,13 +26,13 @@ authors = ["Your Name"]
 edition = "2021"
 
 [dependencies]
-gstd = { git = "https://github.com/gear-tech/gear.git", tag = "v1.0.2", features = ["debug"] }
+gstd = { git = "https://github.com/gear-tech/gear.git", tag = "v1.1.1", features = ["debug"] }
 
 [build-dependencies]
-gear-wasm-builder = { git = "https://github.com/gear-tech/gear.git", tag = "v1.0.2" }
+gear-wasm-builder = { git = "https://github.com/gear-tech/gear.git", tag = "v1.1.1" }
 
 [dev-dependencies]
-gclient = { git = "https://github.com/gear-tech/gear.git", tag = "v1.0.2" }
+gclient = { git = "https://github.com/gear-tech/gear.git", tag = "v1.1.1" }
 tokio = { version = "1", features = ["full"] }
 ```
 
@@ -47,18 +47,18 @@ The best way is to download the latest node binary for your operating system fro
 Terminal:
 
 ```bash
-curl https://get.gear.rs/gear-v1.0.2-x86_64-unknown-linux-gnu.tar.xz | tar xJ
+curl https://get.gear.rs/gear-v1.1.1-x86_64-unknown-linux-gnu.tar.xz | tar xJ
 ```
 
 or
 
-**Linux x86-64**: [gear-v1.0.2-x86_64-unknown-linux-gnu.tar.xz](https://get.gear.rs/gear-v1.0.2-x86_64-unknown-linux-gnu.tar.xz)
+**Linux x86-64**: [gear-v1.1.1-x86_64-unknown-linux-gnu.tar.xz](https://get.gear.rs/gear-v1.1.1-x86_64-unknown-linux-gnu.tar.xz)
 
 You can try to run the node:
 
 ```
 ❯ ./gear --version
-gear 1.0.2-d02d306f97c
+gear 1.1.1-33ee05d5aab
 ```
 
 </TabItem>
@@ -68,18 +68,18 @@ gear 1.0.2-d02d306f97c
 Terminal:
 
 ```bash
-curl https://get.gear.rs/gear-v1.0.2-aarch64-apple-darwin.tar.xz | tar xJ
+curl https://get.gear.rs/gear-v1.1.1-aarch64-apple-darwin.tar.xz | tar xJ
 ```
 
 or
 
-**macOS ARM**: [gear-v1.0.2-aarch64-apple-darwin.tar.xz](https://get.gear.rs/gear-v1.0.2-aarch64-apple-darwin.tar.xz)
+**macOS ARM**: [gear-v1.1.1-aarch64-apple-darwin.tar.xz](https://get.gear.rs/gear-v1.1.1-aarch64-apple-darwin.tar.xz)
 
 You can try to run the node:
 
 ```
 ❯ ./gear --version
-gear 1.0.2-d02d306f97c
+gear 1.1.1-33ee05d5aab
 ```
 
 </TabItem>
@@ -88,18 +88,18 @@ gear 1.0.2-d02d306f97c
 Terminal:
 
 ```bash
-curl https://get.gear.rs/gear-v1.0.2-x86_64-apple-darwin.tar.xz | tar xJ
+curl https://get.gear.rs/gear-v1.1.1-x86_64-apple-darwin.tar.xz | tar xJ
 ```
 
 or
 
-**macOS x86-64**: [gear-v1.0.2-x86_64-apple-darwin.tar.xz](https://get.gear.rs/gear-v1.0.2-x86_64-apple-darwin.tar.xz)
+**macOS x86-64**: [gear-v1.1.1-x86_64-apple-darwin.tar.xz](https://get.gear.rs/gear-v1.1.1-x86_64-apple-darwin.tar.xz)
 
 You can try to run the node:
 
 ```
 ❯ ./gear --version
-gear 1.0.2-d02d306f97c
+gear 1.1.1-33ee05d5aab
 ```
 
 </TabItem>
@@ -109,18 +109,18 @@ gear 1.0.2-d02d306f97c
 Terminal:
 
 ```bash
-curl -O https://get.gear.rs/gear-v1.0.2-x86_64-pc-windows-msvc.zip
+curl -O https://get.gear.rs/gear-v1.1.1-x86_64-pc-windows-msvc.zip
 ```
 
 or
 
-**Windows x86-64**: [gear-v1.0.2-x86_64-pc-windows-msvc.zip](https://get.gear.rs/gear-v1.0.2-x86_64-pc-windows-msvc.zip)
+**Windows x86-64**: [gear-v1.1.1-x86_64-pc-windows-msvc.zip](https://get.gear.rs/gear-v1.1.1-x86_64-pc-windows-msvc.zip)
 
 Unzip the downloaded package then you can try to run the node:
 
 ```
 ❯ gear.exe --version
-gear.exe 1.0.2-d02d306f97c
+gear 1.1.1-33ee05d5aab
 ```
 
 </TabItem>

diff --git a/docs/developing-contracts/testing-gtest.md b/docs/developing-contracts/testing-gtest.md
@@ -20,13 +20,13 @@ authors = ["Your Name"]
 edition = "2021"
 
 [dependencies]
-gstd = { git = "https://github.com/gear-tech/gear.git", tag = "v1.0.2" }
+gstd = { git = "https://github.com/gear-tech/gear.git", tag = "v1.1.1" }
 
 [build-dependencies]
-gear-wasm-builder = { git = "https://github.com/gear-tech/gear.git", tag = "v1.0.2" }
+gear-wasm-builder = { git = "https://github.com/gear-tech/gear.git", tag = "v1.1.1" }
 
 [dev-dependencies]
-gtest = { git = "https://github.com/gear-tech/gear.git", tag = "v1.0.2" }
+gtest = { git = "https://github.com/gear-tech/gear.git", tag = "v1.1.1" }
 ```
 
 ## `gtest` capabilities

diff --git a/docs/examples/prerequisites.mdx b/docs/examples/prerequisites.mdx
@@ -19,8 +19,7 @@ All program examples and JS applications have been tested on a stable environmen
 
 You may configure a local development environment according to the information provided below or use a pre-configured Docker image as described in the [Using Docker](#using-docker) section.
 
-Current stable release: `v1.0.2`
-
+Current stable release: `v1.1.1`
 
 <table>
 <tr>
@@ -70,7 +69,7 @@ Gear Rust libraries: `gstd`, `gtest`, `gmeta`, `gclient`, `gear-wasm-builder`
 </td>
 <td>
 
-v1.0.2
+v1.1.1
 </td>
 <td>
 
@@ -102,17 +101,17 @@ Make sure you are connected to the Vara Network Testnet. You may switch the netw
 </tr>
 <tr>
 <td>Gear JS API</td>
-<td>0.35.2</td>
+<td>0.36.3</td>
 <td>Make sure this version is specified in the package.json file of your program repository</td>
 </tr>
 <tr>
 <td>Gear JS React Hooks</td>
-<td>0.9.2</td>
+<td>0.10.3</td>
 <td>Make sure this version is specified in the package.json file of your program repository</td>
 </tr>
 <tr>
 <td>Gear JS UI Kit</td>
-<td>0.5.19</td>
+<td>0.5.22</td>
 <td>Make sure this version is specified in the package.json file of your program repository</td>
 </tr>
 </table>
@@ -126,6 +125,8 @@ It is highly recommended to use Linux or macOS for compiling Gear node and progr
 
 | Gear node version | Runtime version | Gear libraries version | Rust toolchain version |
 | ----------------- | --------------- | ---------------------- | ---------------------- |
+| v1.0.5            | 1050            | tag = "v1.0.5"         | nightly-2023-09-18     |
+| v1.0.2            | 1020            | tag = "v1.0.2"         | nightly-2023-10-14     |
 | v1.0.1            | 1010            | tag = "v1.0.1"         | nightly-2023-10-14     |
 | v1.0.0            | 1000            | tag = "v1.0.0"         | nightly-2023-04-25     |
 | v0.3.3            | 330             | tag = "v0.3.3"         | nightly-2023-04-25     |

diff --git a/docs/getting-started-in-5-minutes.md b/docs/getting-started-in-5-minutes.md
@@ -33,19 +33,19 @@ This guide provides a general overview of running programs on the networks power
     curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
     ```
 
-3. Now, let's install a `nightly` version of the toolchain with `rustup`, since Gear uses the most up-to-date features `rustup` provides. We use `nightly-2023-09-18` as it is the latest version that is compatible with Gear.
+3. Install a `nightly` version of the toolchain with `rustup`, since Gear uses the most up-to-date features `rustup` provides. `nightly-2023-09-18` is the latest version compatible with Gear.
 
     ```bash
     rustup toolchain add nightly-2023-09-18
     ```
 
-4. As we will be compiling a Rust program to Wasm, we will need a Wasm compiler. Let's add it to the toolchain.
+4. Aa Wasm compiler is necessary for compiling a Rust program to Wasm, add it to the toolchain.
 
     ```bash
     rustup target add wasm32-unknown-unknown --toolchain nightly-2023-09-18
     ```
 
-5. Also, you need to install the `wasm-proc` utility that optimizes compiled Wasm to be more compact.
+5. Install the `wasm-proc` utility that optimizes compiled Wasm to be more compact.
 
     ```bash
     cargo install --locked --git https://github.com/gear-tech/gear.git wasm-proc
@@ -61,14 +61,14 @@ This guide provides a general overview of running programs on the networks power
     mkdir -p ~/gear
     ```
 
-2. Let's create a `contracts` directory inside `gear` and `cd` to it.
+2. Create a `contracts` directory inside `gear` and `cd` to it.
 
     ```bash
     mkdir -p ~/gear/contracts
     cd ~/gear/contracts
     ```
 
-3. The next step would be to build a Rust library for our program:
+3. Build a Rust library for the program:
 
     ```bash
     cargo new counter --lib
@@ -104,7 +104,7 @@ This guide provides a general overview of running programs on the networks power
 
     [dependencies]
     # highlight-next-line
-    gstd = { git = "https://github.com/gear-tech/gear.git", tag = "v1.0.2" }
+    gstd = { git = "https://github.com/gear-tech/gear.git", tag = "v1.1.1" }
     ```
 
 6. Replace the default contents of `lib.rs` in the `counter` folder with the code for our first program.
@@ -144,7 +144,7 @@ This guide provides a general overview of running programs on the networks power
         cargo +nightly-2023-09-18 build --release --target=wasm32-unknown-unknown
     ```
 
-    This command is quite verbose, so we can create cargo config and Rust toolchain override files to make it shorter. Create a `.cargo/config.toml` file in the `counter` directory with the following contents:
+    This command is quite verbose, so you can create cargo config and Rust toolchain override files to make it shorter. Create a `.cargo/config.toml` file in the `counter` directory with the following contents:
 
     ```toml
     [build]
@@ -164,7 +164,7 @@ This guide provides a general overview of running programs on the networks power
     profile = "default"
     ```
 
-    Now you can build your program with a single command:
+    Now build your program with a single command:
 
     ```bash
     cargo build --release
@@ -181,7 +181,7 @@ This guide provides a general overview of running programs on the networks power
             └── counter.wasm    <---- this is our built .wasm file
     ```
 
-8. The last preparation step is to optimize the Wasm binary using `wasm-proc`:
+8. The last step is to optimize the Wasm binary using `wasm-proc`:
 
     ```bash
     wasm-proc target/wasm32-unknown-unknown/release/counter.wasm

diff --git a/docs/node/multi-node.md b/docs/node/multi-node.md
@@ -26,8 +26,8 @@ Note: this will require two terminal sessions (one for each node).
 
   ```
   Gear Node
-  ✌️ version 1.0.2-d02d306f97c
-  ❤️ by Gear Technologies, 2021-2023
+  ✌️ version 1.1.1-d02d306f97c
+  ❤️ by Gear Technologies, 2021-2024
   📋 Chain specification: Vara Local Testnet
   🏷 Node name: Alice
   👤 Role: AUTHORITY
@@ -72,13 +72,13 @@ Note: this will require two terminal sessions (one for each node).
 
   ```
   Gear Node
-  ✌️ version 1.0.2-d02d306f97c
-  ❤️ by Gear Technologies, 2021-2023
+  ✌️ version 1.1.1-33ee05d5aab
+  ❤️ by Gear Technologies, 2021-2024
   📋 Chain specification: Vara Local Testnet
   🏷 Node name: Bob
   👤 Role: AUTHORITY
   💾 Database: RocksDb at /tmp/bob/chains/gear_local_testnet/db/full
-  ⛓ Native runtime: vara-1020 (vara-1.tx1.au1)
+  ⛓ Native runtime: vara-1110 (vara-1.tx1.au1)
   🔨 Initializing Genesis block/state (state: 0xf470…d2dc, header-hash: 0x22c7…6847)
   👴 Loading GRANDPA authority set from genesis on what appears to be first startup.
   👶 Creating empty BABE epoch changes on what appears to be first startup.

diff --git a/docs/node/node-as-service.md b/docs/node/node-as-service.md
@@ -100,7 +100,7 @@ After the node has been running for a while, you may need to update it to the la
 You just need to replace the node executable (`gear`) with the latest version and restart the execution. For example, if your Linux executable is located at `/usr/bin/gear` (as we've configured above) you are to run:
 
 ```
-curl https://get.gear.rs/gear-v1.0.2-x86_64-unknown-linux-gnu.tar.xz | sudo tar -xJC /usr/bin
+curl https://get.gear.rs/gear-v1.1.1-x86_64-unknown-linux-gnu.tar.xz | sudo tar -xJC /usr/bin
 sudo systemctl restart gear-node
 ```
 

diff --git a/docs/node/node-faq.md b/docs/node/node-faq.md
@@ -52,7 +52,7 @@ For example you can use this manual: https://community.hetzner.com/tutorials/blo
 You just need to replace the node executable (`gear`) with the latest version and restart the execution. For example, if your Linux executable is located at `/usr/bin` you are to run:
 
 ```shell
-curl https://get.gear.rs/gear-v1.0.2-x86_64-unknown-linux-gnu.tar.xz | sudo tar -xJC /usr/bin
+curl https://get.gear.rs/gear-v1.1.1-x86_64-unknown-linux-gnu.tar.xz | sudo tar -xJC /usr/bin
 sudo systemctl restart gear-node
 ```