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

build(deps): bump github.com/linxGnu/grocksdb from 1.8.10 to 1.8.11 #123

Merged
merged 4 commits into from
Jan 24, 2024

Conversation

faddat
Copy link
Contributor

@faddat faddat commented Jan 24, 2024

This PR bumps RocksDB in the Dockerfile and should permit the merge of #119

Itr's also been updated to contain #119 for simplicity's sake, and so that we can see the results in CI.

dependabot bot and others added 2 commits January 11, 2024 11:21
Bumps [github.com/linxGnu/grocksdb](https://github.com/linxGnu/grocksdb) from 1.8.10 to 1.8.11.
- [Release notes](https://github.com/linxGnu/grocksdb/releases)
- [Commits](linxGnu/grocksdb@v1.8.10...v1.8.11)

---
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>
@faddat faddat requested a review from a team as a code owner January 24, 2024 14:53
@faddat faddat changed the title Update rocksdb in Dockerfile Update rocksdb in Dockerfile and update grocksdb Jan 24, 2024
@melekes melekes changed the title Update rocksdb in Dockerfile and update grocksdb build(deps): bump github.com/linxGnu/grocksdb from 1.8.10 to 1.8.11 Jan 24, 2024
@melekes
Copy link
Contributor

melekes commented Jan 24, 2024

Thanks @faddat ❤️

@melekes melekes added this pull request to the merge queue Jan 24, 2024
Merged via the queue into cometbft:main with commit 649c0ef Jan 24, 2024
8 checks passed
@adizere adizere added this to the 2024-Q1 milestone Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants