This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/cargo/rust/tokio-1.52.0
in repository https://gitbox.apache.org/repos/asf/arrow-adbc.git
discard f1dc7281d chore(rust): bump tokio from 1.51.0 to 1.52.0 in /rust
add 0ae0a1098 chore(go/adbc): bump cloud.google.com/go/bigquery from
1.75.0 to 1.76.0 in /go/adbc (#4216)
add a2d32de09 chore(go/adbc): bump github.com/snowflakedb/gosnowflake from
1.19.0 to 1.19.1 in /go/adbc (#4220)
add 9b24ae6cd chore(rust): bump test-with from 0.16.0 to 0.16.1 (#4221)
add 94bb0198e chore(java): bump com.uber.nullaway:nullaway from 0.13.2 to
0.13.3 (#4214)
add b3175bab4 chore(rust): bump tokio from 1.51.0 to 1.52.0 in /rust
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 (f1dc7281d)
\
N -- N -- N refs/heads/dependabot/cargo/rust/tokio-1.52.0
(b3175bab4)
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 | 6 +-
go/adbc/go.sum | 28 +-
java/pom.xml | 2 +-
rust/Cargo.lock | 1549 ++------------------------------------
rust/driver/snowflake/Cargo.toml | 2 +-
5 files changed, 85 insertions(+), 1502 deletions(-)
