This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch update/influxdb-java-2.25
in repository https://gitbox.apache.org/repos/asf/pekko-connectors.git
discard 43428eccc Update influxdb-java to 2.25
add f5b3b263e Update auth, dynamodb, eventbridge, firehose, ... to 2.32.4
(#1123)
add 2cb6de4d2 Update netty-handler to 4.2.3.Final (#1122)
add 1368b8a12 Update commons-io to 2.20.0 (#1121)
add ebe43c4d1 Update google-cloud-pubsub to 1.141.0 (#1120)
add cc3927f93 Update jackson-module-scala to 2.19.2 (#1119)
add 7641f4637 pekko 1.1.5 (#1118)
add 9d121586d Update influxdb-java to 2.25
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 (43428eccc)
\
N -- N -- N refs/heads/update/influxdb-java-2.25 (9d121586d)
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:
project/Dependencies.scala | 10 +++++-----
project/PekkoCoreDependency.scala | 2 +-
2 files changed, 6 insertions(+), 6 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
