This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/cargo/rust/arrow-datafusion-b54c33cb47
in repository https://gitbox.apache.org/repos/asf/arrow-adbc.git
discard a2ee17c6c chore(rust): Bump the arrow-datafusion group in /rust with 6
updates
add 1268635d5 chore(go/adbc): Bump golang.org/x/tools from 0.40.0 to
0.41.0 (#3880)
add cf7b5cab1 chore(java): Bump com.google.protobuf:protobuf-java from
4.33.2 to 4.33.4 (#3883)
add 873a043c1 chore(rust): Bump toml from 0.9.10+spec-1.1.0 to
0.9.11+spec-1.1.0 in /rust (#3885)
add 8ba658940 chore(rust): Bump the arrow-datafusion group in /rust with 6
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 (a2ee17c6c)
\
N -- N -- N
refs/heads/dependabot/cargo/rust/arrow-datafusion-b54c33cb47 (8ba658940)
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:
go/adbc/go.mod | 16 ++++++++--------
go/adbc/go.sum | 32 ++++++++++++++++----------------
java/driver/flight-sql/pom.xml | 2 +-
rust/Cargo.lock | 4 ++--
rust/driver_manager/Cargo.toml | 2 +-
5 files changed, 28 insertions(+), 28 deletions(-)
