bump version

ethersphere · Jun 1, 2021 · 7a52ab0 · 7a52ab0
1 parent 4ab59c0
commit 7a52ab0
Show file tree

Hide file tree

Showing 6 changed files with 29 additions and 28 deletions.
diff --git a/docs/installation/build-from-source.md b/docs/installation/build-from-source.md
@@ -35,7 +35,7 @@ git describe --tags
 3) Checkout the required version:
 
 ```bash
-git checkout v0.6.1
+git checkout v0.6.2
 ```
 
 4) Build the binary:
@@ -51,7 +51,7 @@ dist/bee version
 ```
 
 ```
-0.6.0
+0.6.2
 ```
 
 6) (optional) Additionally, you may also like to move the Bee binary to somewhere in your `$PATH`

diff --git a/docs/installation/docker.md b/docs/installation/docker.md
@@ -71,7 +71,7 @@ docker pull ethersphere/bee:beta
 #### Specific Versions
 
 ```bash
-docker pull ethersphere/bee:0.6.0
+docker pull ethersphere/bee:0.6.2
 ```
 
 #### Edge
@@ -91,13 +91,13 @@ Configuration files for Bee and Bee Clef are provided to enable quick and easy i
 First, retrieve the current `docker-compose.yaml` file.
 
 ```bash
-wget -q https://raw.githubusercontent.com/ethersphere/bee/v0.6.1/packaging/docker/docker-compose.yml
+wget -q https://raw.githubusercontent.com/ethersphere/bee/v0.6.2/packaging/docker/docker-compose.yml
 ```
 
 Next, create a `.env` file using the example file provided. This file will be responsible for storing configuration and secrets for our Bee and Bee Clef applications.
 
 ```bash
-wget -q https://raw.githubusercontent.com/ethersphere/bee/v0.6.1/packaging/docker/env -O .env
+wget -q https://raw.githubusercontent.com/ethersphere/bee/v0.6.2/packaging/docker/env -O .env
 ``` 
 
 There are some important configuration parameters which must be set in order for our projects to work. To affect configuration in the `.env` file, we first remove the `#` at the beginning of the line and then change the value after `=` to our desired config.

diff --git a/docs/installation/install.md b/docs/installation/install.md
@@ -158,24 +158,24 @@ Next, install Bee itself, simply choose the appropriate command from the ones be
 #### AMD64
 
 ```bash
-wget https://github.com/ethersphere/bee/releases/download/v0.6.1/bee_0.6.0_amd64.deb
-sudo dpkg -i bee_0.6.0_amd64.deb
+wget https://github.com/ethersphere/bee/releases/download/v0.6.2/bee_0.6.2_amd64.deb
+sudo dpkg -i bee_0.6.2_amd64.deb
 ```
 
 #### ARM (Raspberry Pi)
 
 ##### ARMv7
 
 ```bash
-wget https://github.com/ethersphere/bee/releases/download/v0.6.1/bee_0.6.0_armv7.deb
-sudo dpkg -i bee_0.6.0_armv7.deb
+wget https://github.com/ethersphere/bee/releases/download/v0.6.2/bee_0.6.2_armv7.deb
+sudo dpkg -i bee_0.6.2_armv7.deb
 ```
 
 ##### ARM64
 
 ```bash
-wget https://github.com/ethersphere/bee/releases/download/v0.6.1/bee_0.6.0_arm64.deb
-sudo dpkg -i bee_0.6.0_arm64.deb
+wget https://github.com/ethersphere/bee/releases/download/v0.6.2/bee_0.6.2_arm64.deb
+sudo dpkg -i bee_0.6.2_arm64.deb
 ```
 </TabItem>
 <TabItem value="centos">
@@ -185,24 +185,24 @@ sudo dpkg -i bee_0.6.0_arm64.deb
 #### AMD64
 
 ```bash
-wget https://github.com/ethersphere/bee/releases/download/v0.6.1/bee_0.6.0_amd64.rpm
-sudo rpm -i bee_0.6.0_amd64.rpm
+wget https://github.com/ethersphere/bee/releases/download/v0.6.2/bee_0.6.2_amd64.rpm
+sudo rpm -i bee_0.6.2_amd64.rpm
 ```
 
 #### ARM (Raspberry Pi)
 
 ##### ARMv7
 
 ```bash
-wget https://github.com/ethersphere/bee/releases/download/v0.6.1/bee_0.6.0_armv7.rpm
-sudo rpm -i bee_0.6.0_armv7.rpm
+wget https://github.com/ethersphere/bee/releases/download/v0.6.2/bee_0.6.2_armv7.rpm
+sudo rpm -i bee_0.6.2_armv7.rpm
 ```
 
 ##### ARM64
 
 ```bash
-wget https://github.com/ethersphere/bee/releases/download/v0.6.1/bee_0.6.0_arm64.rpm
-sudo rpm -i bee_0.6.0_arm64.rpm
+wget https://github.com/ethersphere/bee/releases/download/v0.6.2/bee_0.6.2_arm64.rpm
+sudo rpm -i bee_0.6.2_arm64.rpm
 ```
 </TabItem>
 <TabItem value="macos">
@@ -284,6 +284,7 @@ Then configure your node, including your p2p port (usually 1634).
 ```yaml
 nat-addr: "123.123.123.123:1634"
 ```
+
 #### Debug API
 
 For a new installation of Bee, the debug API endpoint is not yet exposed for security reasons. To enable the debug API endpoints, set `debug-api-enable` to `true` in your [configuration file](/docs/working-with-bee/configuration) and restart your Bee service.

diff --git a/docs/installation/manual.md b/docs/installation/manual.md
@@ -17,12 +17,12 @@ To install the binary using our quick install script, run either one of the foll
 
 #### wget
 ```bash
-wget -q -O - https://raw.githubusercontent.com/ethersphere/bee/master/install.sh | TAG=v0.6.1 bash
+wget -q -O - https://raw.githubusercontent.com/ethersphere/bee/master/install.sh | TAG=v0.6.2 bash
 ```
 
 #### curl
 ```bash
-curl -s https://raw.githubusercontent.com/ethersphere/bee/master/install.sh | TAG=v0.6.1 bash
+curl -s https://raw.githubusercontent.com/ethersphere/bee/master/install.sh | TAG=v0.6.2 bash
 ```
 
 ### Run Bee
@@ -34,7 +34,7 @@ bee version
 ```
 
 ```
-0.6.0
+0.6.2
 ```
 
 Now your Bee node is installed, you can fund your node with gBZZ join us in the swarm! 🐝 🐝 🐝 🐝 🐝

diff --git a/docs/installation/rasp-bee-ry-pi.md b/docs/installation/rasp-bee-ry-pi.md
@@ -53,8 +53,8 @@ We must install Bee Clef before Bee. To do so, open the browser (the 🌐 icon)
 Click `Install > Bee Clef` and scroll down to find the installation commands for Bee Clef **ARM (Raspberry Pi) ARMv7**. These should look something like: 
 
 ```sh
-wget https://github.com/ethersphere/bee/releases/download/v0.6.1/bee_0.6.0_armv7.deb
-sudo dpkg -i bee_0.6.0_armv7.deb
+wget https://github.com/ethersphere/bee/releases/download/v0.6.2/bee_0.6.2_armv7.deb
+sudo dpkg -i bee_0.6.2_armv7.deb
 ```
 
 Click `copy` on the right hand side of the box containing the instructions, then go back to your terminal on your Raspberry Pi, right click with your mouse and paste in the commands. The first one will execute immediately because there is a 'newline' or 'enter' character. 
@@ -131,7 +131,7 @@ Your output should looks something like this:
 
 ```bash
 -rw-r--r--  1 pi   pi       3523 Mar  4 22:47 .bashrc
--rw-r--r--  1 pi   pi   10787806 Mar 23 08:18 bee_0.6.0_armv7.deb
+-rw-r--r--  1 pi   pi   10787806 Mar 23 08:18 bee_0.6.2_armv7.deb
 -rw-r--r--  1 pi   pi   10473282 Feb 24 18:00 bee-clef_0.4.12_armv7.deb
 drwxr-xr-x  2 pi   pi       4096 Mar  4 22:57 Bookshelf
 ```
@@ -141,7 +141,7 @@ For more information, you can use the `man` utility to read the manual. Type `ma
 Now, let's use the `rm` programme to remove the clutter and delete the `.deb` files we no longer need.
 
 ```bash
-rm bee_0.6.0_armv7.deb
+rm bee_0.6.2_armv7.deb
 ```
 
 The `rm` programme gives no output, so let's check it's dissapeared by checking the contents of the directory. This time we will also you the 'pipe' command, which passes the output of one command to the next, and the `grep` command which searches through the output and only prints lines that match the pattern.

diff --git a/docs/working-with-bee/upgrade.md b/docs/working-with-bee/upgrade.md
@@ -12,13 +12,13 @@ Bee sure to [backup](/docs/working-with-bee/backups) your clef key material and
 
 ### Upgrading from 0.5.x Series to 0.6.x
 
-Bee 0.6.0 contains a few breaking changes which mean a database migration must take place. We also intoduce [postage stamps](/docs/access-the-swarm/keep-your-data-alive) which must be attached to chunks of data so that they will be retained in the Swarm network.
+Bee 0.6.2 contains a few breaking changes which mean a database migration must take place. We also intoduce [postage stamps](/docs/access-the-swarm/keep-your-data-alive) which must be attached to chunks of data so that they will be retained in the Swarm network.
 
 :::info
 Please take note that nodes which deployed their chequebook with bee v0.5.0 will have to be started with the --transaction TXHASH flag where TXHASH is any Ethereum transaction on goerli network sent from the bee node's Ethereum address. The hash of the chequebook deployment transaction can be used for this and can be looked up on etherscan. For nodes which first started with v0.5.1 or higher no action is necessary, as their chequebook deployment transaction will be automatically picked-up by the Bee node. 
 :::
 
-As part of these changes, if you have any **locally pinned content**, this must be manually migrated to the new data structure expected by the network of 0.6.0 clients, see below for information on how to proceed. 
+As part of these changes, if you have any **locally pinned content**, this must be manually migrated to the new data structure expected by the network of 0.6.2 clients, see below for information on how to proceed. 
 
 If you *do not* have any locally pinned content, your migration will be automatic and your update will proceed as normal.
 
@@ -44,7 +44,7 @@ To update **without pinned content:**
 4. Adjust your configuration. Several configuration parameters have changed in 0.6.x - If you wish to continue running as a full node, you must set the new `full-node` flag to `true`. check out the [configuration](/docs/working-with-bee/configuration) guide for more info on how to update your configuration.
 5. Restart your node.
 
-Your Bee should start up as normal, and begin to connect to other Bees that are running Bee 0.6.0 or later.
+Your Bee should start up as normal, and begin to connect to other Bees that are running Bee 0.6.2 or later.
 
 #### Manual Migration Procedure
 
@@ -56,7 +56,7 @@ Your Bee should start up as normal, and begin to connect to other Bees that are
 6. Adjust your configuration. Several configuration parameters have changed in 0.6.x - If you wish to continue running as a full node, you must set the new `full-node` flag to `true`. check out the [configuration](/docs/working-with-bee/configuration) guide for more info on how to update your configuration.
 7. Restart your node.
 
-Your Bee should start up as normal, and begin to connect to other Bees that are running Bee 0.6.0 or later.
+Your Bee should start up as normal, and begin to connect to other Bees that are running Bee 0.6.2 or later.
 
 ## Upgrade Procedure