-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Require correct gogo import paths (backport #14852) #14853
docs: Require correct gogo import paths (backport #14852) #14853
Conversation
(cherry picked from commit 6a441f3) # Conflicts: # UPGRADING.md
Preparing the changelog and the release notes here too. |
@@ -80,6 +80,16 @@ Please use the `ghcr.io/cosmos/proto-builder` image (version >= `0.11.5`) for ge | |||
|
|||
See which buf commit for `cosmos/cosmos-sdk` to pin in your `buf.yaml` file [here](./proto/README.md). | |||
|
|||
#### Gogoproto Import Paths |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: to put at the correct place in main, when adding v047 changelog to main.
@@ -8,7 +8,7 @@ require ( | |||
cosmossdk.io/depinject v1.0.0-alpha.3 | |||
cosmossdk.io/math v1.0.0-beta.4 | |||
cosmossdk.io/tools/rosetta v0.2.0 | |||
github.com/cosmos/cosmos-sdk v0.47.0-alpha2 | |||
github.com/cosmos/cosmos-sdk v0.47.0-rc2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing this so it shows the correct version when going to http://127.0.0.1:1317/cosmos/base/tendermint/v1beta1/node_info
from simapp built in the v0.47 branch.
It has no other effect, as we use a replace directive.
Tagging a rc2 after this is merged. |
This is an automatic backport of pull request #14852 done by Mergify.
Cherry-pick of 6a441f3 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com