This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/cargo/core/rocksdb-0.22.0
in repository https://gitbox.apache.org/repos/asf/opendal.git
discard b96bc9d50e chore(deps): bump rocksdb from 0.21.0 to 0.22.0 in /core
add ca25b3c679 chore(deps): bump crate-ci/typos from 1.22.9 to 1.23.6
(#4948)
add 5140ff5b7c chore(deps): bump tokio from 1.39.1 to 1.39.2 in /bin/oli
(#4949)
add 5f035683e9 chore(deps): bump bytes from 1.6.1 to 1.7.0 in /bin/ofs
(#4947)
add e2a8f2d155 chore(deps): bump tokio from 1.39.1 to 1.39.2 in /bin/oay
(#4946)
add 84a4ce381a feat: impl `put_multipart` in `object_store` (#4793)
add 72db76ba0f chore(deps): bump rocksdb from 0.21.0 to 0.22.0 in /core
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (b96bc9d50e)
\
N -- N -- N refs/heads/dependabot/cargo/core/rocksdb-0.22.0
(72db76ba0f)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.github/workflows/ci_check.yml | 2 +-
bin/oay/Cargo.lock | 4 +-
bin/oay/Cargo.toml | 2 +-
bin/ofs/Cargo.lock | 4 +-
bin/ofs/Cargo.toml | 2 +-
bin/oli/Cargo.lock | 4 +-
bin/oli/Cargo.toml | 2 +-
core/Cargo.lock | 888 +++++++++++++++------------------
integrations/object_store/Cargo.toml | 1 +
integrations/object_store/src/store.rs | 176 ++++++-
integrations/object_store/src/utils.rs | 8 +-
11 files changed, 579 insertions(+), 514 deletions(-)
