Skip to content
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

Merged
merged 8 commits into from
Oct 3, 2021

Conversation

evan-forbes
Copy link
Member

@evan-forbes evan-forbes commented Sep 29, 2021

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

evan-forbes and others added 6 commits January 12, 2021 06:55
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 <braveryandglory@gmail.com>

* use latest commit of celestia-core

* add version that was somehow missing?

Co-authored-by: Nguyen Nhu Viet <braveryandglory@gmail.com>
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 <robert@zaremba.ch>
(cherry picked from commit f757c90)

# Conflicts:
#	CHANGELOG.md

* Update CHANGELOG.md

Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>
Co-authored-by: Robert Zaremba <robert@zaremba.ch>
* CL: create v0.44.1

* Add releaes notes

* Update date

* Update RELEASE_NOTES.md

Co-authored-by: Robert Zaremba <robert@zaremba.ch>

* mark abci.QueryRequest as bugfix

Co-authored-by: Robert Zaremba <robert@zaremba.ch>
@evan-forbes evan-forbes self-assigned this Sep 29, 2021
@evan-forbes evan-forbes changed the title Create cosmos-sdk branch that uses Celestia and is based on v.0.44.0 of upstream chore: Create cosmos-sdk branch that uses Celestia and is based on v.0.44.0 of upstream Sep 29, 2021
@liamsi
Copy link
Member

liamsi commented Sep 30, 2021

There has been a patch release btw: https://github.com/cosmos/cosmos-sdk/releases/tag/v0.44.1

@liamsi
Copy link
Member

liamsi commented Sep 30, 2021

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
The tags (for our releases) should also be the same and additionally, contain a suffix (like previously -lazy or sth like that)

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.

@evan-forbes evan-forbes changed the base branch from evan/upstream-v0.44.0-base to release/v0.44.x-celestia September 30, 2021 15:14
@evan-forbes
Copy link
Member Author

Also, I'd like our branches from which we create the releases from to match those with upstream

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.

Copy link
Member

@tzdybal tzdybal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@evan-forbes evan-forbes merged commit 51997c8 into release/v0.44.x-celestia Oct 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants