diff options
| author | Andrew Kryczka <andrewkr@fb.com> | 2021-02-05 17:01:51 -0800 |
|---|---|---|
| committer | Andrew Kryczka <andrewkr@fb.com> | 2021-02-05 17:01:51 -0800 |
| commit | abd4b1ff1504ae2a7ed6e60bc9c9797b880c33a5 (patch) | |
| tree | 53575d28f29875c19f6794bbe46fb0a7f7e48201 | |
| parent | 5893d5e2a1f27dcdc2ca74f06a7fdb207be0237a (diff) | |
bump version and update HISTORY.md for 6.15.5v6.15.5
| -rw-r--r-- | HISTORY.md | 2 | ||||
| -rw-r--r-- | include/rocksdb/version.h | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/HISTORY.md b/HISTORY.md index 643c745d6..731cb4530 100644 --- a/HISTORY.md +++ b/HISTORY.md @@ -1,5 +1,5 @@ # Rocksdb Change Log -## Unreleased +## 6.15.5 (02/05/2021) ### Bug Fixes * Since 6.15.0, `TransactionDB` returns error `Status`es from calls to `DeleteRange()` and calls to `Write()` where the `WriteBatch` contains a range deletion. Previously such operations may have succeeded while not providing the expected transactional guarantees. There are certain cases where range deletion can still be used on such DBs; see the API doc on `TransactionDB::DeleteRange()` for details. * `OptimisticTransactionDB` now returns error `Status`es from calls to `DeleteRange()` and calls to `Write()` where the `WriteBatch` contains a range deletion. Previously such operations may have succeeded while not providing the expected transactional guarantees. diff --git a/include/rocksdb/version.h b/include/rocksdb/version.h index 5e86dd596..75533791b 100644 --- a/include/rocksdb/version.h +++ b/include/rocksdb/version.h @@ -6,7 +6,7 @@ #define ROCKSDB_MAJOR 6 #define ROCKSDB_MINOR 15 -#define ROCKSDB_PATCH 4 +#define ROCKSDB_PATCH 5 // Do not use these. We made the mistake of declaring macros starting with // double underscore. Now we have to live with our choice. We'll deprecate these |