This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch 
dependabot/go_modules/go/adbc/google.golang.org/grpc-1.76.0
in repository https://gitbox.apache.org/repos/asf/arrow-adbc.git


 discard 170fca8a0 chore(go/adbc): Bump google.golang.org/grpc in /go/adbc
     add 97bbe60d4 chore(java): Bump com.microsoft.sqlserver:mssql-jdbc from 
13.2.0.jre11 to 13.2.1.jre11 in /java (#3566)
     add b559e7bf2 chore(go/adbc): Bump modernc.org/sqlite from 1.39.0 to 
1.39.1 in /go/adbc (#3564)
     add 88b8b2f54 chore: Bump ruby/setup-ruby from 1.263.0 to 1.265.0 (#3560)
     add 594fc85a4 chore(go/adbc): Bump google.golang.org/grpc 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   (170fca8a0)
            \
             N -- N -- N   
refs/heads/dependabot/go_modules/go/adbc/google.golang.org/grpc-1.76.0 
(594fc85a4)

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/packaging.yml                 |  2 +-
 go/adbc/go.mod                                  |  4 ++--
 go/adbc/go.sum                                  | 20 ++++++++++----------
 java/driver/jdbc-validation-mssqlserver/pom.xml |  2 +-
 4 files changed, 14 insertions(+), 14 deletions(-)

Reply via email to