This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/go_modules/go/adbc/github.com/apache/arrow/go/v17-17.0.0
in repository https://gitbox.apache.org/repos/asf/arrow-adbc.git
discard 16e5e046d chore(go/adbc): bump github.com/apache/arrow/go/v17 in
/go/adbc
add 402eb0629 chore(csharp): bump Apache.Arrow from 16.1.0 to 17.0.0 in
/csharp (#2030)
add 94e952ea0 chore(csharp): bump DuckDB.NET.Bindings.Full from 1.0.1 to
1.0.2 in /csharp (#2031)
add 2ef37040d chore(go/adbc): bump google.golang.org/api from 0.188.0 to
0.189.0 in /go/adbc (#2032)
add fc0e52a89 chore(java): bump com.google.errorprone:error_prone_core
from 2.28.0 to 2.29.2 in /java (#2037)
add 893f17094 chore(java): bump
org.apache.maven.plugins:maven-javadoc-plugin from 3.7.0 to 3.8.0 in /java
(#2036)
add bf987c63d chore(go/adbc): bump cloud.google.com/go/bigquery from
1.61.0 to 1.62.0 in /go/adbc (#2034)
add 7c55dbc82 chore(go/adbc): bump github.com/apache/arrow/go/v17 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 (16e5e046d)
\
N -- N -- N
refs/heads/dependabot/go_modules/go/adbc/github.com/apache/arrow/go/v17-17.0.0
(7c55dbc82)
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:
.../src/Apache.Arrow.Adbc/Apache.Arrow.Adbc.csproj | 2 +-
.../Apache.Arrow.Adbc.Tests.csproj | 2 +-
go/adbc/go.mod | 16 +++++-----
go/adbc/go.sum | 36 +++++++++++-----------
java/pom.xml | 4 +--
5 files changed, 30 insertions(+), 30 deletions(-)
