This is an automated email from the ASF dual-hosted git repository.
asukaminato pushed a change to branch dependabot/cargo/core/others-bb31f4d231
in repository https://gitbox.apache.org/repos/asf/opendal.git
discard 487bd9e11 .build()
discard c65bcccdb clippy
discard ac7c2964a chore(deps): bump the others group in /core with 15 updates
add ffb3857a1 chore(deps): bump the logs-errors-checksums group in /core
with 2 updates (#6635)
add c6e8963a3 chore(deps): bump the pyo3 group in /bindings/python with 2
updates (#6631)
add 5bb506aca chore(deps): bump the third-party-actions group with 2
updates (#6636)
add 189f19839 chore(deps): bump the others group in /core with 15 updates
add d75adc2fa clippy
add 10d587522 .build()
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 (487bd9e11)
\
N -- N -- N refs/heads/dependabot/cargo/core/others-bb31f4d231
(10d587522)
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 +-
.github/workflows/docs.yml | 2 +-
.github/workflows/test_behavior_binding_python.yml | 2 +-
bindings/python/Cargo.toml | 4 ++--
bindings/python/src/file.rs | 10 +++++-----
bindings/python/src/lister.rs | 6 +++---
bindings/python/src/operator.rs | 8 ++++----
bindings/python/src/utils.rs | 2 +-
core/Cargo.lock | 8 ++++----
core/Cargo.toml | 2 +-
core/fuzz/Cargo.toml | 2 +-
11 files changed, 24 insertions(+), 24 deletions(-)
