-
Notifications
You must be signed in to change notification settings - Fork 34
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
chore: Create cosmos-sdk branch that uses Celestia and is based on v.0.44.0 of upstream #34
chore: Create cosmos-sdk branch that uses Celestia and is based on v.0.44.0 of upstream #34
Conversation
Update from upstream (after v0.40.0)
* manually swith to lazyledger-core * manually replace tendermint with lazyledger-core in all proto files update proto to lazyleder-core * baseapp: delete old tendermint abci method * baseapp: partially implement new ABCI method baseapp: add todo for PreprocessTxs docs * bubble new error, switch to field instead of method, and replace old tendermint function with std lib go mod tidy * server: fixed bug that stops config from being unmarshalled by viper * fix tag to allow for proper unmarshalling * regenerate proto bindings * use the latest version of lazyledger-core to fix the grpc versioning issue causing panics * add template test for the new abci method finish doc sentence * update changelog * running gofmt -s
* use celestiaorg instead of lazyledger * try some changes to fix go mod * use older version of golang/mock in order to get tests to pass * use the branch of celestia-core that restores some unused code (will use master later) * regenerate proto files * fix links Co-authored-by: Nguyen Nhu Viet <[email protected]> * use latest commit of celestia-core * add version that was somehow missing? Co-authored-by: Nguyen Nhu Viet <[email protected]>
cosmos#10189) (cosmos#10253) * fix: removed potential sources of non-determinism in upgrades (cosmos#10189) forced deterministic iteration order in upgrade migrations, x/upgrade and store during upgrades Co-authored-by: Robert Zaremba <[email protected]> (cherry picked from commit f757c90) # Conflicts: # CHANGELOG.md * Update CHANGELOG.md Co-authored-by: Tomas Tauber <[email protected]> Co-authored-by: Robert Zaremba <[email protected]>
* CL: create v0.44.1 * Add releaes notes * Update date * Update RELEASE_NOTES.md Co-authored-by: Robert Zaremba <[email protected]> * mark abci.QueryRequest as bugfix Co-authored-by: Robert Zaremba <[email protected]>
There has been a patch release btw: https://github.com/cosmos/cosmos-sdk/releases/tag/v0.44.1 |
Also, I'd like our branches from which we create the releases from to match those with upstream, e.g.: https://github.com/cosmos/cosmos-sdk/tree/release/v0.44.x That way it is clear where the version we are using originated from, and which version our release is based on. Also, we can pull updates right from the original branch. Same for tendermint. Maybe we should capture this in some markdown file somehow. |
f1d7264
to
9f78578
Compare
9f78578
to
aada8f6
Compare
sounds good! 👍 switched the base of this branch to the latest from upstream v.044.x and also updated this PR branch, so we are now using the patch version along with appropriate naming. |
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.
LGTM.
Description
celestia-app will need a stable version of the sdk to point to, therefore we will also need a stable release branch of the sdk that uses celestia-core instead of tendermint. This PR introduces the minimum changes necessary to do just that.
part of #27