Bump default chdb latest release version to 2.0.0b0 #12
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
|
|
|
Sorry I forgot to mention the tests were not passing. And I'm not that familiar with what's happening there 🙁 |
|
Thanks for your PR! |
auxten
changed the title
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.
When installing
chdb-nodethe defaultchdbversion theupdate_libchdb.shscript installs is 1.1.0.This PR bumps that default version to the current latest release of
chdb: 1.4.1.You could comment/un-comment the
LATEST_RELEASEvariable in the script but I believe most people want to be in control of thechdbversion they use.Also I bumped the
chdb-nodeversion to 1.1.4 as I don't think there are any breaking changes betweenchdb1.1.0 and 1.4.1 but happy to change it to 1.2.0 if you think it's more appropriate.