This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/java/org.apache-apache-36
in repository https://gitbox.apache.org/repos/asf/arrow-adbc.git
discard 010375db6 chore(java): Bump org.apache:apache from 35 to 36 in /java
add e767d1eac chore: Bump the actions group with 2 updates (#3864)
add ad7c17b7f chore(rust): Bump url from 2.5.7 to 2.5.8 in /rust (#3865)
add 9aaa7759a chore(rust): Bump tokio from 1.48.0 to 1.49.0 in /rust
(#3866)
add 537a7bea0 chore(java): Bump org.junit:junit-bom from 5.14.1 to 5.14.2
(#3862)
add fd3aae84a chore(go/adbc): Bump google.golang.org/api from 0.258.0 to
0.259.0 in /go/adbc (#3861)
add 046417de2 chore(java): Bump the linters group with 2 updates (#3869)
add d187b7475 chore(java): Bump org.apache:apache from 35 to 36 in /java
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 (010375db6)
\
N -- N -- N
refs/heads/dependabot/maven/java/org.apache-apache-36 (d187b7475)
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/integration.yml | 2 +-
.github/workflows/packaging.yml | 2 +-
go/adbc/go.mod | 12 ++++++------
go/adbc/go.sum | 36 ++++++++++++++++++------------------
java/pom.xml | 4 ++--
rust/Cargo.lock | 8 ++++----
rust/driver/datafusion/Cargo.toml | 2 +-
rust/driver/snowflake/Cargo.toml | 2 +-
8 files changed, 34 insertions(+), 34 deletions(-)
