This is an automated email from the ASF dual-hosted git repository.
asukaminato pushed a change to branch
dependabot/cargo/bindings/python/pyo3-dependencies-6370ace62f
in repository https://gitbox.apache.org/repos/asf/opendal.git
discard 378b92c69 chore(deps): bump the pyo3-dependencies group
add 33770df26 chore(deps): bump toml from 0.8.22 to 0.8.23 in /bin/oli
(#6361)
add 475437788 chore(deps): bump mlugg/setup-zig from 2.0.1 to 2.0.3 (#6359)
add 14ad488e0 chore(deps): bump axios from 1.8.2 to 1.10.0 in /website
(#6363)
add 56c70c909 chore(deps): bump tokio from 1.45.0 to 1.45.1 in /bin/oay
(#6358)
add 19d706235 chore(deps): bump the pyo3-dependencies group
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 (378b92c69)
\
N -- N -- N
refs/heads/dependabot/cargo/bindings/python/pyo3-dependencies-6370ace62f
(19d706235)
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_bindings_zig.yml | 2 +-
bin/oay/Cargo.lock | 4 +-
bin/oay/Cargo.toml | 2 +-
bin/oli/Cargo.lock | 20 ++++----
website/DEPENDENCIES.node.csv | 2 +-
website/package.json | 2 +-
website/pnpm-lock.yaml | 94 +++++++++++++++++++++++------------
7 files changed, 79 insertions(+), 47 deletions(-)
