-
Notifications
You must be signed in to change notification settings - Fork 70
chore: bump Go MSRV to 1.22 and grocksdb version #146
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 Go MSRV to 1.22 and grocksdb version #146
Conversation
faddat
commented
Apr 4, 2024
- build(deps): bump github.com/linxGnu/grocksdb from 1.8.12 to 1.8.14
- update rocksdb in the dockerfile that the tests run in
Bumps [github.com/linxGnu/grocksdb](https://github.com/linxGnu/grocksdb) from 1.8.12 to 1.8.14. - [Release notes](https://github.com/linxGnu/grocksdb/releases) - [Commits](linxGnu/grocksdb@v1.8.12...v1.8.14) --- updated-dependencies: - dependency-name: github.com/linxGnu/grocksdb dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #146 +/- ##
==========================================
+ Coverage 76.80% 78.12% +1.31%
==========================================
Files 23 23
Lines 2048 1714 -334
==========================================
- Hits 1573 1339 -234
+ Misses 403 298 -105
- Partials 72 77 +5 |
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.
@@ -18,7 +18,7 @@ RUN apt update \ | |||
libleveldb-dev libleveldb1d | |||
|
|||
FROM build AS install | |||
ARG ROCKSDB=8.9.1 | |||
ARG ROCKSDB=8.11.3 |
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.
looks good cf. https://github.com/linxGnu/grocksdb/releases/tag/v1.8.14
The release that we use has to match the release in grocksdb, so we would want to use 13 for now |
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.
👍