This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/cargo/core/http-serialization-utils-f1cf52f783
in repository https://gitbox.apache.org/repos/asf/opendal.git
omit 2a1962928 chore(deps): bump the http-serialization-utils group
add 8ab1e28f0 chore(deps): bump syn from 2.0.100 to 2.0.117 in /dev (#7846)
add fe63ec9b4 chore(deps): bump minijinja from 2.5.0 to 2.21.0 in /dev
(#7845)
add 4beb36b57 chore(deps): bump semver from 1.0.25 to 1.0.27 in /dev
(#7842)
add 9d892d404 chore(deps): bump flate2 from 1.1.0 to 1.1.9 in /dev (#7843)
add 25eee0797 chore(deps): bump the others group in /core with 6 updates
(#7847)
add f9ccce351 chore(deps): bump clap from 4.5.23 to 4.5.60 in /dev (#7844)
add bc15f62f3 chore(deps): bump the http-serialization-utils group across
1 directory with 3 updates
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 (2a1962928)
\
N -- N -- N
refs/heads/dependabot/cargo/core/http-serialization-utils-f1cf52f783 (bc15f62f3)
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:
core/Cargo.lock | 285 +++++++++++++++++++---------------
core/layers/hotpath/Cargo.toml | 2 +-
core/services/foundationdb/Cargo.toml | 2 +-
dev/Cargo.lock | 71 ++++-----
4 files changed, 194 insertions(+), 166 deletions(-)
