From d30e79d4bdf3df6823dc3a5807a65edbe5e61e5e Mon Sep 17 00:00:00 2001 From: MSalopek Date: Fri, 19 Jul 2024 13:40:58 +0200 Subject: [PATCH 1/2] docs: update upgrading v5.1.0 --- UPGRADING.md | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/UPGRADING.md b/UPGRADING.md index f6e856bba5..9aa62c943a 100644 --- a/UPGRADING.md +++ b/UPGRADING.md @@ -1,5 +1,39 @@ # Upgrading Replicated Security +## [v5.1.x](https://github.com/cosmos/interchain-security/releases/tag/v5.1.0) + +### Provider + +***Note that providers using v5.0.0 cannot upgrade to v5.1.0 cleanly*** + +Providers using versions `v4.0.x`, `v4.1.x`, `v4.2.x`, `v4.3.x` and `v4.4.x` can upgrade to `v5.1.0`. + +Upgrading from `v4.x` to `v5.1.0` will upgrade the provider `consensus version` to 7. + +Upgrade code will be executed automatically during the upgrade procedure. + +### Consumer + +Upgrading the consumer from `v5.0.0` to `v5.1.0` will not require state migration. + +This guide provides instructions for upgrading to specific versions of Replicated Security. + +## [v5.0.0](https://github.com/cosmos/interchain-security/releases/tag/v5.0.0) + +### Provider + +***Note that providers should not be using this release*** + +v5.0.0 was a **consumer only release**. + +### Consumer + +Upgrading the consumer from `v4.x` to `v5.0.0` will require state migrations. + +Consumer versions `v4.0.x`, `v4.1.x`,, `v4.2.x`, `v4.3.x` and `v4.4.x` can cleanly be upgraded to `v5.0.0`. + +Upgrade code will be executed automatically during the upgrade procedure. + ## [v4.4.x](https://github.com/cosmos/interchain-security/releases/tag/v4.4.0) ### Provider From 5301e51810669f8a4d09b6c63dba628a6699473a Mon Sep 17 00:00:00 2001 From: MSalopek Date: Fri, 19 Jul 2024 13:56:39 +0200 Subject: [PATCH 2/2] Update UPGRADING.md --- UPGRADING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/UPGRADING.md b/UPGRADING.md index 9aa62c943a..1f25aa3d08 100644 --- a/UPGRADING.md +++ b/UPGRADING.md @@ -6,7 +6,7 @@ ***Note that providers using v5.0.0 cannot upgrade to v5.1.0 cleanly*** -Providers using versions `v4.0.x`, `v4.1.x`, `v4.2.x`, `v4.3.x` and `v4.4.x` can upgrade to `v5.1.0`. +Providers using versions `v4.0.x`, `v4.1.x`, `v4.2.x`, `v4.3.x` and `v4.4.x` can upgrade to `v5.1.0`. Upgrading from `v4.x` to `v5.1.0` will upgrade the provider `consensus version` to 7. @@ -30,7 +30,7 @@ v5.0.0 was a **consumer only release**. Upgrading the consumer from `v4.x` to `v5.0.0` will require state migrations. -Consumer versions `v4.0.x`, `v4.1.x`,, `v4.2.x`, `v4.3.x` and `v4.4.x` can cleanly be upgraded to `v5.0.0`. +Consumer versions `v4.0.x`, `v4.1.x`, `v4.2.x`, `v4.3.x` and `v4.4.x` can cleanly be upgraded to `v5.0.0`. Upgrade code will be executed automatically during the upgrade procedure.