-
Notifications
You must be signed in to change notification settings - Fork 925
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: bump celestia-app to v1.0.0-rc2 #2305
chore: bump celestia-app to v1.0.0-rc2 #2305
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2305 +/- ##
=======================================
Coverage 50.55% 50.56%
=======================================
Files 154 154
Lines 9733 9736 +3
=======================================
+ Hits 4921 4923 +2
Misses 4385 4385
- Partials 427 428 +1
|
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.
Approving!
We need to cleanup the usage of this constant, thus #2309
@evan-forbes, linter seems to complain after the merge, do you mind fixing it? |
Head branch was pushed to by a user without write access
sorry forgot to mention @Wondertan fixed in 46e2a70 also bumped to rc2 since why not |
Overview
bumps app to latest release candidate. I'm not sure how celestia-node wants to handle app version changes. I'm completely unaware of any existing plans, so aplogies if this is already planned for, but ideally we don't rely on the latest appversion constant. This is definitely fine for v1, but when v2 comes along we will want to change which version we use according to what is in the header.
Checklist