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 642368e19 Update influxdb-java to 2.25
add 0a4fd2467 Update auth, dynamodb, eventbridge, firehose, ... to 2.37.3
(#1279)
add 096f23ca8 Update scalafmt-core to 3.10.1 (#1278)
add 12813fd7e Update sbt-scalafmt to 2.5.6 (#1277)
add 1b21907e5 Update jackson-module-scala to 2.20.1 (#1276)
add ebafefcbd use latest version of circe (#1275)
add 910d61a60 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 (642368e19)
\
N -- N -- N refs/heads/update/influxdb-java-2.25 (910d61a60)
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:
.scalafmt.conf | 2 +-
project/Dependencies.scala | 7 ++++---
project/plugins.sbt | 2 +-
3 files changed, 6 insertions(+), 5 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]