Skip to content

Commit

Permalink
nits
Browse files Browse the repository at this point in the history
  • Loading branch information
sainoe committed Jul 26, 2024
1 parent 864f50b commit 94d0445
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
10 changes: 5 additions & 5 deletions UPGRADING.md
Original file line number Diff line number Diff line change
@@ -1,20 +1,20 @@
# Upgrading Replicated Security

## [v5.1.x](https://github.com/cosmos/interchain-security/releases/tag/v5.1.0)
## [v5.1.x](https://github.com/cosmos/interchain-security/releases/tag/v5.1.1)

### Provider

***Note that providers using v5.0.0 cannot upgrade to v5.1.0 cleanly***
***Note that providers using v5.0.0 cannot upgrade to v5.1.1 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.1`.

Upgrading from `v4.x` to `v5.1.0` will upgrade the provider `consensus version` to 7.
Upgrading from `v4.x` to `v5.1.1` 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.
Upgrading the consumer from `v5.0.0` to `v5.1.1` will not require state migration.

This guide provides instructions for upgrading to specific versions of Replicated Security.

Expand Down
2 changes: 1 addition & 1 deletion docs/docs/upgrading/migrate_v4_v5.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Pre-requisite version for this upgrade: any from the `v4.x` release line.

`v5.0.0` should not be used on the provider.

The provider should be updated to `v5.1.0`.
The provider should be updated to `v5.1.1`.

## Provider

Expand Down

0 comments on commit 94d0445

Please sign in to comment.