This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/go_modules/go/adbc/cloud.google.com/go/bigquery-1.75.0
in repository https://gitbox.apache.org/repos/asf/arrow-adbc.git
omit 676d92bef chore(go/adbc): Bump cloud.google.com/go/bigquery in /go/adbc
add 3d050b91a chore(rust): bump tokio from 1.50.0 to 1.51.0 in /rust
(#4192)
add 71295184d chore(go/adbc): bump the opentelemetry group across 1
directory with 6 updates (#4188)
add c4358405f docs: improve docs for homebrew post-release task (#4186)
add 6ee2435e6 chore(go/adbc): bump google.golang.org/api (#4189)
add b5b944b5f chore(go/adbc): Bump cloud.google.com/go/bigquery in /go/adbc
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 (676d92bef)
\
N -- N -- N
refs/heads/dependabot/go_modules/go/adbc/cloud.google.com/go/bigquery-1.75.0
(b5b944b5f)
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:
docs/source/development/releasing.rst | 17 +++++++--
go/adbc/go.mod | 34 ++++++++---------
go/adbc/go.sum | 72 +++++++++++++++++------------------
rust/Cargo.lock | 12 +++---
rust/driver/datafusion/Cargo.toml | 2 +-
5 files changed, 74 insertions(+), 63 deletions(-)
