(pekko-connectors) branch update/jcl-over-slf4j-2.0.12 updated (f57037e52 -> 0c8327dec)

[gi...@apache.org]

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

github-bot pushed a change to branch update/jcl-over-slf4j-2.0.12
in repository https://gitbox.apache.org/repos/asf/pekko-connectors.git


    omit f57037e52 Update jcl-over-slf4j, log4j-over-slf4j to 2.0.12
     add 0d3ba1f49 Update auth, dynamodb, eventbridge, firehose, ... to 2.25.16 (#583)
     add 9b199b854 Update amazon-kinesis-client to 2.5.7 (#584)
     add 23b233a9c Update netty-handler to 4.1.108.Final (#582)
     add 2c69b7edc remove incubator footer (#585)
     add 07f6cc096 need build to be able to access snapshot jars (#587)
     add 0c8327dec Update jcl-over-slf4j, log4j-over-slf4j to 2.0.12

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   (f57037e52)
            \
             N -- N -- N   refs/heads/update/jcl-over-slf4j-2.0.12 (0c8327dec)

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:
 build.sbt                  | 3 ++-
 project/Dependencies.scala | 6 +++---
 2 files changed, 5 insertions(+), 4 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pekko.apache.org
For additional commands, e-mail: commits-help@pekko.apache.org