Skip to content

Commit 0538ed4

Browse files
mergify[bot]MSalopeksainoe
authored
docs: update upgrading v5.1.0 (backport #2071) (#2072)
docs: update upgrading v5.1.0 (#2071) * docs: update upgrading v5.1.0 * Update UPGRADING.md (cherry picked from commit d05eae2) Co-authored-by: MSalopek <matija.salopek994@gmail.com> Co-authored-by: Simon Noetzlin <simon.ntz@gmail.com>
1 parent 16256d1 commit 0538ed4

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed

UPGRADING.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,39 @@
11
# Upgrading Replicated Security
22

3+
## [v5.1.x](https://github.com/cosmos/interchain-security/releases/tag/v5.1.0)
4+
5+
### Provider
6+
7+
***Note that providers using v5.0.0 cannot upgrade to v5.1.0 cleanly***
8+
9+
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`.
10+
11+
Upgrading from `v4.x` to `v5.1.0` will upgrade the provider `consensus version` to 7.
12+
13+
Upgrade code will be executed automatically during the upgrade procedure.
14+
15+
### Consumer
16+
17+
Upgrading the consumer from `v5.0.0` to `v5.1.0` will not require state migration.
18+
19+
This guide provides instructions for upgrading to specific versions of Replicated Security.
20+
21+
## [v5.0.0](https://github.com/cosmos/interchain-security/releases/tag/v5.0.0)
22+
23+
### Provider
24+
25+
***Note that providers should not be using this release***
26+
27+
v5.0.0 was a **consumer only release**.
28+
29+
### Consumer
30+
31+
Upgrading the consumer from `v4.x` to `v5.0.0` will require state migrations.
32+
33+
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`.
34+
35+
Upgrade code will be executed automatically during the upgrade procedure.
36+
337
## [v4.4.x](https://github.com/cosmos/interchain-security/releases/tag/v4.4.0)
438

539
### Provider

0 commit comments

Comments
 (0)