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/incubator-pekko-connectors.git
omit 79e78efc9 Update jcl-over-slf4j, log4j-over-slf4j to 2.0.12
add acb5808c7 Update auth, dynamodb, eventbridge, firehose, ... to 2.23.21
(#477)
add 1697079d1 Update solr-solrj, solr-test-framework to 8.11.3 (#474)
add 951d83918 Update google-auth-library-credentials, ... to 1.23.0 (#472)
add 387fa3f4b Update scalatest to 3.2.18 (#475)
add 4e08c002b mqtt import order (#486)
add bb9afc1a4 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 (79e78efc9)
\
N -- N -- N refs/heads/update/jcl-over-slf4j-2.0.12 (bb9afc1a4)
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:
.../pekko/stream/connectors/mqtt/impl/MqttFlowStage.scala | 4 ++--
.../org/apache/pekko/stream/connectors/mqtt/settings.scala | 2 +-
project/Dependencies.scala | 11 ++++++-----
3 files changed, 9 insertions(+), 8 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
