This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch update/arrow-memory-netty-16.1.0
in repository https://gitbox.apache.org/repos/asf/pekko-connectors.git
omit ed73df012 Update arrow-memory-netty, arrow-vector to 16.1.0
add 12c55be5f Update auth, dynamodb, eventbridge, firehose, ... to 2.25.60
(#673)
add 7b147ac3f Update spring-context, spring-core to 5.3.36 (#672)
add 703aed445 Update java-driver-core to 4.18.1 (#671)
add f31256e66 Update netty-handler to 4.1.110.Final (#670)
add 48ecd19f2 Update orientdb-graphdb, orientdb-object to 3.2.30 (#669)
add 71f2070e5 build with pekko http 1.1 (#667)
add 934989257 fix link-validator.yml (#676)
add c7deffbcf Update arrow-memory-netty, arrow-vector to 16.1.0
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 (ed73df012)
\
N -- N -- N refs/heads/update/arrow-memory-netty-16.1.0
(c7deffbcf)
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/link-validator.yml | 3 +++
project/Dependencies.scala | 12 ++++++------
project/PekkoCoreDependency.scala | 2 +-
project/PekkoHttpDependency.scala | 2 +-
4 files changed, 11 insertions(+), 8 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
