Sync ibc-go at e1df7a6948d1dd94b7d2dadd226bee23d3e1e667 #172
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Farhad-Shabani
approved these changes
Jan 8, 2024
Farhad-Shabani
deleted the
carlos/sync-ibc-go-e1df7a6948d1dd94b7d2dadd226bee23d3e1e667
branch
romac
added a commit
that referenced
this pull request
Jan 9, 2024
romac
added a commit
that referenced
this pull request
Jan 9, 2024
Farhad-Shabani
added a commit
that referenced
this pull request
Jan 9, 2024
* release v0.41.0 * chore: update changelog & summary * Remove changelog entry for #172 --------- Co-authored-by: Romain Ruetschi <romain@informal.systems>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sync ibc-go with e1df7a6948d1dd94b7d2dadd226bee23d3e1e667.
Main reason for me to open this PR is to get
counterparty_upgrade_sequenceinMsgTimeoutOnCloseandMsgChannelCloseConfirmso that I can add support for handling this field in hermes. This is required for properly closing channels after a channel has gone through a channel upgrade. cc: @ljoss17This is the first I attempt doing this, so please let me know if I am missing something...