chore: update regen binary version in upgrade guide

Author: aleem1314

docs/validators/upgrades/v7.0-upgrade.md

@@ -6,7 +6,7 @@ This document provides guidelines for node operators upgrading from Regen Ledger
 
 ### Regen Ledger v7.0
 
-- [Release Notes](https://github.com/regen-network/regen-ledger/releases/tag/v7.1.0)
+- [Release Notes](https://github.com/regen-network/regen-ledger/releases/tag/v7.2.0)
 
 ### Regen Mainnet
 
@@ -31,12 +31,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 (`v7.1.0`) from source:
+Build the upgrade binary (`v7.2.0`) from source:
 
 ```bash
 cd regen-ledger
 git fetch --tags
-git checkout v7.1.0
+git checkout v7.2.0
 make build
 ```
 
@@ -49,10 +49,10 @@ Ensure the `regen` binary has been built:
 You should see the following:
 
 ```bash
-v7.1.0
+v7.2.0
 ```
 
-Create a `v7_0` directory and copy the upgrade binary (`v7.1.0`) to the directory:
+Create a `v7_0` directory and copy the upgrade binary (`v7.2.0`) to the directory:
 
 ```bash
 mkdir -p $HOME/.regen/cosmovisor/upgrades/v7_0/bin
@@ -67,21 +67,21 @@ $HOME/.regen/cosmovisor/upgrades/v7_0/bin/regen version
 You should see the following:
 
 ```bash
-v7.1.0
+v7.2.0
 ```
 
-At the proposed block height, `cosmovisor` will automatically stop the current binary (`v6.x.x`), set the upgrade binary as the current binary (`v7.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 (`v6.x.x`), set the upgrade binary as the current binary (`v7.2.0`), 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 (`v7.1.0`) from source:
+First Build the upgrade binary (`v7.2.0`) from source:
 
 ```bash
 cd regen-ledger
 git fetch --tags
-git checkout v7.1.0
+git checkout v7.2.0
 make install
 ```
 
@@ -94,7 +94,7 @@ regen version
 You should see the following:
 
 ```bash
-v7.1.0
+v7.2.0
 ```
 
 When the chain halts at the proposed upgrade height, stop the current process running `regen`.