Skip to content

Commit

Permalink
Update changelog
Browse files Browse the repository at this point in the history
  • Loading branch information
romac committed Nov 13, 2023
1 parent cfb1226 commit eff587d
Show file tree
Hide file tree
Showing 5 changed files with 43 additions and 0 deletions.
12 changes: 12 additions & 0 deletions .changelog/v1.7.1/summary.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
This patch release of Hermes now allows operators to set the clearing interval
at a different value for each chain, using the new per-chain `clear_interval` setting.
The global `clear_interval` setting is used as a default value if the per-chain
setting is not defined.

Additionnaly, operators can now set override the CometBFT compatibility mode to be used
for a chain by using the new `compat_mode` per-chain setting. The main use case for this,
is to override the automatically detected compatibility mode in case Hermes gets it wrong
or encounters a non-standard version number and falls back on the wrong CometBFT version.

On top of that, Hermes will now attempt to save on fees by not building a client update
for a given height if the consensus state for that height is already present on chain.
31 changes: 31 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,36 @@
# CHANGELOG

## v1.7.1

*November 13th, 2023*

This patch release of Hermes now allows operators to set the clearing interval
at a different value for each chain, using the new per-chain `clear_interval` setting.
The global `clear_interval` setting is used as a default value if the per-chain
setting is not defined.

Additionnaly, operators can now set override the CometBFT compatibility mode to be used
for a chain by using the new `compat_mode` per-chain setting. The main use case for this,
is to override the automatically detected compatibility mode in case Hermes gets it wrong
or encounters a non-standard version number and falls back on the wrong CometBFT version.

On top of that, Hermes will now attempt to save on fees by not building a client update
for a given height if the consensus state for that height is already present on chain.

### FEATURES

- Add an optional per-chain setting `compat_mode`, which can be
used to specify which CometBFT compatibility mode is used for interacting with the node over RPC.
([\#3623](https://github.com/informalsystems/hermes/issues/3623))
- Add a configuration which allows to override the `clear_interval` for specific
chains ([\#3691](https://github.com/informalsystems/hermes/issues/3691))

### IMPROVEMENTS

- Hermes now saves on fees by not including a client update if the
consensus state at desired height is already present on chain.
([\#3521](https://github.com/informalsystems/hermes/issues/3521))

## v1.7.0

*October 20th, 2023*
Expand Down

0 comments on commit eff587d

Please sign in to comment.