(pekko-connectors-kafka) branch update/scala3-library-3.3.4 updated (f9635a37 -> a25e4c2c)

[gi...@apache.org]

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

github-bot pushed a change to branch update/scala3-library-3.3.4
in repository https://gitbox.apache.org/repos/asf/pekko-connectors-kafka.git


 discard f9635a37 Update scala3-library to 3.3.4
     add 6179d2e0 Update junit-jupiter-api to 5.11.1 (#234)
     add d29dc319 getContainerIpAddress is deprecated (#237)
     add a3600104 release notes for v1.1.0 (#225)
     add a25e4c2c Update scala3-library to 3.3.4

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   (f9635a37)
            \
             N -- N -- N   refs/heads/update/scala3-library-3.3.4 (a25e4c2c)

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:
 .github/workflows/publish-1.1-docs.yml                         | 10 +++++-----
 build.sbt                                                      |  2 +-
 docs/src/main/paradox/release-notes/releases-1.1.md            |  7 +++----
 .../kafka/testkit/internal/PekkoConnectorsKafkaContainer.java  |  5 ++---
 .../pekko/kafka/testkit/internal/SchemaRegistryContainer.java  |  3 +--
 5 files changed, 12 insertions(+), 15 deletions(-)


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