You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A release notes template that should be adapted for every release
3
-
- release: <v*.*.*>
4
-
- release branch: <v*.x>
5
-
- the last release: <v-last>
6
-
- the last release branch: <v-last.x>
7
-
-->
8
-
9
-
# Replicated Security <v*.*.*> Release Notes
1
+
# Replicated Security v4.1.0 Release Notes
10
2
11
3
<!--
12
4
Please indicate whether this release is relevant to consumers or providers.
13
5
-->
14
-
❗ ***Note this release is ONLY relevant to <consumers/providers>***
6
+
❗ ***Note this release is ONLY relevant to providers***
15
7
16
8
## 📝 Changelog
17
-
** REMOVE THE LINE BELOW TO ENABLE THE MARKDOWN LINK CHECKER FOR RELEASE **
18
-
<!-- markdown-link-check-disable -->
19
-
20
-
Check out the [changelog](https://github.com/cosmos/interchain-security/blob/<v*.*.*>/CHANGELOG.md) for a list of relevant changes or [compare all changes](https://github.com/cosmos/interchain-security/compare/release/<v-last>...<v*.*.*>) from last release.
9
+
Check out the [changelog](https://github.com/cosmos/interchain-security/blob/v4.1.0/CHANGELOG.md) for a list of relevant changes or [compare all changes](https://github.com/cosmos/interchain-security/compare/v4.0.0...v4.1.0) from last release.
21
10
22
11
<!-- Add the following line for major releases -->
23
-
Refer to the [upgrading guide](https://github.com/cosmos/interchain-security/blob/release/<v*.x>/UPGRADING.md) when migrating from `<v-last.x>` to `<v*.x>`.
12
+
Refer to the [upgrading guide](https://github.com/cosmos/interchain-security/blob/release/v4.1.x/UPGRADING.md) when migrating from `v4.0.x` to `v4.1.x`.
24
13
25
-
** REMOVE THE LINE BELOW TO ENABLE THE MARKDOWN LINK CHECKER FOR RELEASE **
26
-
<!-- markdown-link-check-enable -->
27
14
## 🚀 Highlights
28
-
29
-
<!-- Add any highlights of this release -->
30
-
31
-
## ❤️ Contributors
32
-
<!-- markdown-link-check-disable -->
33
-
* Informal Systems ([@informalinc](https://twitter.com/informalinc))
34
-
<!-- markdown-link-check-enable -->
35
-
36
-
This list is non-exhaustive and ordered alphabetically.
37
-
Thank you to everyone who contributed to this release!
15
+
This release introduces epochs that reduce the costs of relaying IBC packets for ICS.
16
+
In addition it introduces queries to retrieve the send timestamp of the oldest unconfirmed VSCPacket by chain id and
Copy file name to clipboardExpand all lines: UPGRADING.md
+14-14Lines changed: 14 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
This guide provides instructions for upgrading to specific versions of Replicated Security.
4
4
5
-
## [v4.1.x](https://github.com/cosmos/interchain-security/releases/tag/v4.1.0-rc2) and [v4.1.x-lsm](https://github.com/cosmos/interchain-security/releases/tag/v4.1.0-lsm-rc2)
5
+
## [v4.1.x](https://github.com/cosmos/interchain-security/releases/tag/v4.1.0) and [v4.1.x-lsm](https://github.com/cosmos/interchain-security/releases/tag/v4.1.0-lsm)
6
6
7
7
### Provider
8
8
@@ -15,17 +15,17 @@ as well as the corresponding migrators [here](https://github.com/cosmos/intercha
`v4.0.x` sets the minimum required version of Go to `1.21`, see https://github.com/cosmos/interchain-security/blob/release/v4.0.x/go.mod#L3.
18
+
`v4.0.x` sets the minimum required version of Go to `1.21`, see https://github.com/cosmos/interchain-security/blob/release/v4.0.x/go.mod#L3.
19
19
20
-
### Provider
20
+
### Provider
21
21
22
-
Upgrading a provider from `v3.3.0` to `v4.0.0` will require state migrations, see https://github.com/cosmos/interchain-security/blob/release/v4.0.x/x/ccv/provider/migrations/migrator.go#L31.
22
+
Upgrading a provider from `v3.3.0` to `v4.0.0` will require state migrations, see https://github.com/cosmos/interchain-security/blob/release/v4.0.x/x/ccv/provider/migrations/migrator.go#L31.
23
23
24
-
### Consumer
24
+
### Consumer
25
25
26
-
***Note that consumer chains can upgrade directly from `v3.1.0` to `v4.0.0`.***
26
+
***Note that consumer chains can upgrade directly from `v3.1.0` to `v4.0.0`.***
27
27
28
-
Upgrading a consumer from `v3.2.0` to `v4.0.0` will not require state migration, however, upgrading directly from `v3.1.0` to `v4.0.0` will require state migrations, see https://github.com/cosmos/interchain-security/blob/release/v4.0.x/x/ccv/consumer/keeper/migrations.go#L22.
28
+
Upgrading a consumer from `v3.2.0` to `v4.0.0` will not require state migration, however, upgrading directly from `v3.1.0` to `v4.0.0` will require state migrations, see https://github.com/cosmos/interchain-security/blob/release/v4.0.x/x/ccv/consumer/keeper/migrations.go#L22.
29
29
30
30
In addition, the following migration needs to be added to the upgrade handler of the consumer chain:
`v3.2.0` bumps IBC to `v7.3`. As a result, `legacy_ibc_testing` is not longer required and was removed, see https://github.com/cosmos/interchain-security/pull/1185. This means that when upgrading to `v3.2.0`, any customized tests relying on `legacy_ibc_testing` need to be updated.
59
59
60
-
### Consumer
60
+
### Consumer
61
61
62
62
Upgrading the consumer from either `v3.0.0` or `v3.1.0` to `v3.2.0` will require state migrations, see https://github.com/cosmos/interchain-security/blob/release/v3.2.x/x/ccv/consumer/keeper/migration.go#L25.
63
63
@@ -67,13 +67,13 @@ Upgrading the consumer from either `v3.0.0` or `v3.1.0` to `v3.2.0` will require
67
67
68
68
The following should be considered as complementary to [Cosmos SDK v0.47 UPGRADING.md](https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc2/UPGRADING.md).
69
69
70
-
#### Protobuf
70
+
#### Protobuf
71
71
72
72
Protobuf code generation, linting and formatting have been updated to leverage the `ghcr.io/cosmos/proto-builder:0.11.5` docker container. Replicated Security protobuf definitions are now packaged and published to [buf.build/cosmos/interchain-security](https://buf.build/cosmos/interchain-security) via CI workflows. The `third_party/proto` directory has been removed in favour of dependency management using [buf.build](https://docs.buf.build/introduction).
73
73
74
74
#### App modules
75
75
76
-
Legacy APIs of the `AppModule` interface have been removed from ccv modules. For example, for
76
+
Legacy APIs of the `AppModule` interface have been removed from ccv modules. For example, for
Upgrading a provider from `v1.1.0-multiden` to `v2.0.0` will require state migrations. See [migration.go](https://github.com/cosmos/interchain-security/blob/v2.0.0/x/ccv/provider/keeper/migration.go).
129
129
130
130
### Consumer
131
131
132
-
Upgrading a consumer from `v1.2.0-multiden` to `v2.0.0` will NOT require state migrations.
132
+
Upgrading a consumer from `v1.2.0-multiden` to `v2.0.0` will NOT require state migrations.
0 commit comments