Skip to content

Commit

Permalink
docs: bump version in v5.1 upgrade guide (#1931)
Browse files Browse the repository at this point in the history
  • Loading branch information
ryanchristo authored May 31, 2023
1 parent 2240baf commit 362e134
Showing 1 changed file with 9 additions and 9 deletions.
18 changes: 9 additions & 9 deletions docs/validators/upgrades/v5.1-upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,12 +34,12 @@ The following instructions assume the `cosmovisor` binary is already installed a
Cosmovisor provides an auto-download option that prevents the need for the following steps in preparing for the upgrade. Although available to validators, this feature should only be used for non-validator nodes and validators should build the binary from source.
:::

Build the upgrade binary (`v5.1.0`) from source:
Build the upgrade binary (`v5.1.1`) from source:

```bash
cd regen-ledger
git fetch --tags
git checkout v5.1.0
git checkout v5.1.1
make build
```

Expand All @@ -52,10 +52,10 @@ Ensure the `regen` binary has been built:
You should see the following:

```bash
v5.1.0
v5.1.1
```

Create a `v5.1` directory and copy the upgrade binary (`v5.1.0`) to the directory:
Create a `v5.1` directory and copy the upgrade binary (`v5.1.1`) to the directory:

```bash
mkdir -p $HOME/.regen/cosmovisor/upgrades/v5.1/bin
Expand All @@ -70,21 +70,21 @@ $HOME/.regen/cosmovisor/upgrades/v5.1/bin/regen version
You should see the following:

```bash
v5.1.0
v5.1.1
```

At the proposed block height, `cosmovisor` will automatically stop the current binary (`v5.0.x`), set the upgrade binary as the current binary (`v5.1.0`), and then (depending on the cosmovisor settings) perform a backup and restart the node.
At the proposed block height, `cosmovisor` will automatically stop the current binary (`v5.0.x`), set the upgrade binary as the current binary (`v5.1.1`), and then (depending on the cosmovisor settings) perform a backup and restart the node.

### Option 2: Without Cosmovisor

Using `cosmovisor` to perform the upgrade is not required. Node operators also have the option to manually update the `regen` binary at the time of the upgrade.

First Build the upgrade binary (`v5.1.0`) from source:
First Build the upgrade binary (`v5.1.1`) from source:

```bash
cd regen-ledger
git fetch --tags
git checkout v5.1.0
git checkout v5.1.1
make install
```

Expand All @@ -97,7 +97,7 @@ regen version
You should see the following:

```bash
v5.1.0
v5.1.1
```

When the chain halts at the proposed upgrade height, stop the current process running `regen`.
Expand Down

0 comments on commit 362e134

Please sign in to comment.