Skip to content

Commit

Permalink
docs: Update v4.1-upgrade.md (#1514)
Browse files Browse the repository at this point in the history
* Update v4.1-upgrade.md

* Update docs/validators/upgrades/v4.1-upgrade.md

Co-authored-by: Kaustubh K <54210167+kaustubhkapatral@users.noreply.github.com>

* Update v4.1-upgrade.md

Co-authored-by: Kaustubh K <54210167+kaustubhkapatral@users.noreply.github.com>
  • Loading branch information
anilcse and kaustubhkapatral authored Oct 2, 2022
1 parent fdd97e0 commit 2268920
Showing 1 changed file with 7 additions and 6 deletions.
13 changes: 7 additions & 6 deletions docs/validators/upgrades/v4.1-upgrade.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
# Upgrade Guide v4.1.2

This document provides guidelines for node operators upgrading from Regen Ledger v4.0 to v4.1.2. For a general overview of the upgrade process, please refer to [Upgrade Overview](README.md).
This document provides guidelines for node operators upgrading from Regen Ledger v4.0 to v4.1.2 (version: `HEAD-5dc0dd2db05af9330bded65eeda778225e72b61c`). For a general overview of the upgrade process, please refer to [Upgrade Overview](README.md).

***Note:*** Pre-build binaries are having version details as `v4.1.2` and the binaries built from source are having the version as `HEAD-5dc0dd2db05af9330bded65eeda778225e72b61c`. Both are referring to the same release.

## Upgrade Info

Expand Down Expand Up @@ -52,7 +54,7 @@ Ensure the `regen` binary has been built:
You should see the following:

```bash
v4.1.2
HEAD-5dc0dd2db05af9330bded65eeda778225e72b61c
```

Create a `v4.1.0` directory and copy the upgrade binary (`v4.1.2`) to the directory:
Expand All @@ -64,16 +66,15 @@ cp ./build/regen $HOME/.regen/cosmovisor/upgrades/v4.1.0/bin
Ensure the right `regen` binary has been placed in the directory:

```bash
$HOME/.regen/cosmovisor/upgrades/v4.1.0/bin
$HOME/.regen/cosmovisor/upgrades/v4.1.0/bin/regen version
```

You should see the following:

```bash
v4.1.2
HEAD-5dc0dd2db05af9330bded65eeda778225e72b61c
```


At the proposed block height, `cosmovisor` will automatically stop the current binary (`v4.0.0`), set the upgrade binary as the current binary (`v4.1.2`), and then (depending on the cosmovisor settings) perform a backup and restart the node.

### Option 2: Without Cosmovisor
Expand All @@ -100,7 +101,7 @@ regen version
You should see the following:

```bash
v4.1.2
HEAD-5dc0dd2db05af9330bded65eeda778225e72b61c
```

Restart the process running `regen`.

0 comments on commit 2268920

Please sign in to comment.