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

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


 discard e5762d5fc Update log4j-to-slf4j to 2.24.0
     add 56b32d3d5 Update auth, dynamodb, eventbridge, firehose, ... to 2.27.24 
(#807)
     add 2acdf0bc1 Update sshj to 0.39.0 (#806)
     add 155c80166 Update google-cloud-pubsub to 1.132.2 (#805)
     add 600516f48 Update proto-google-cloud-bigquerystorage-v1 to 3.9.1 (#804)
     add 53ed673e6 broken link in releases-1.0.md (#803)
     add 32af42fce don't use 'current' for doc links (#808)
     add 2a026cc43 Update log4j-to-slf4j to 2.24.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   (e5762d5fc)
            \
             N -- N -- N   refs/heads/update/log4j-to-slf4j-2.24.0 (2a026cc43)

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                                           |  2 +-
 docs/src/main/paradox/release-notes/releases-1.0.md |  2 +-
 project/Dependencies.scala                          | 12 ++++++------
 3 files changed, 8 insertions(+), 8 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to