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

fanningpj pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pekko-connectors-kafka.git


The following commit(s) were added to refs/heads/main by this push:
     new a3600104 release notes for v1.1.0 (#225)
a3600104 is described below

commit a3600104583f10fe2d9e54806801db54a65edc1c
Author: PJ Fanning <[email protected]>
AuthorDate: Tue Oct 1 19:39:15 2024 +0100

    release notes for v1.1.0 (#225)
    
    * Update releases-1.1.md
    
    * Update publish-1.1-docs.yml
---
 .github/workflows/publish-1.1-docs.yml              | 10 +++++-----
 docs/src/main/paradox/release-notes/releases-1.1.md |  7 +++----
 2 files changed, 8 insertions(+), 9 deletions(-)

diff --git a/.github/workflows/publish-1.1-docs.yml 
b/.github/workflows/publish-1.1-docs.yml
index 2ac837c7..1ec58b86 100644
--- a/.github/workflows/publish-1.1-docs.yml
+++ b/.github/workflows/publish-1.1-docs.yml
@@ -26,19 +26,19 @@ jobs:
 
       - name: Build Documentation
         run: |-
-          sbt "set ThisBuild / version := \"1.1.0-M1\"; docs/paradox; unidoc"
+          sbt "set ThisBuild / version := \"1.1.0\"; docs/paradox; unidoc"
         env:
           JAVA_OPTS: "-verbose:gc -Xmx4g"
 
       # Create directory structure upfront since rsync does not create 
intermediate directories otherwise
       - name: Create directory structure
         run: |-
-          mkdir -p target/nightly-docs/docs/pekko-connectors-kafka/1.1.0-M1/
+          mkdir -p target/nightly-docs/docs/pekko-connectors-kafka/1.1.0/
           mkdir -p target/nightly-docs/docs/pekko-connectors-kafka/1.1/
-          cp -r docs/target/paradox/site/main/ 
target/nightly-docs/docs/pekko-connectors-kafka/1.1.0-M1/docs
+          cp -r docs/target/paradox/site/main/ 
target/nightly-docs/docs/pekko-connectors-kafka/1.1.0/docs
           cp -r docs/target/paradox/site/main/ 
target/nightly-docs/docs/pekko-connectors-kafka/1.1/docs
           rm -r docs/target/paradox/site/main/
-          cp -r target/scala-2.13/unidoc 
target/nightly-docs/docs/pekko-connectors-kafka/1.1.0-M1/api
+          cp -r target/scala-2.13/unidoc 
target/nightly-docs/docs/pekko-connectors-kafka/1.1.0/api
           cp -r target/scala-2.13/unidoc 
target/nightly-docs/docs/pekko-connectors-kafka/1.1/api
           rm -r target/scala-2.13/unidoc
 
@@ -47,7 +47,7 @@ jobs:
         with:
           upload: true
           switches: --archive --compress --update --delete --progress 
--relative
-          local_path: 
target/nightly-docs/./docs/pekko-connectors-kafka/1.1.0-M1 # The intermediate 
dot is to show `--relative` which paths to operate on
+          local_path: target/nightly-docs/./docs/pekko-connectors-kafka/1.1.0 
# The intermediate dot is to show `--relative` which paths to operate on
           remote_path: ${{ secrets.NIGHTLIES_RSYNC_PATH }}/pekko/
           remote_host: ${{ secrets.NIGHTLIES_RSYNC_HOST }}
           remote_port: ${{ secrets.NIGHTLIES_RSYNC_PORT }}
diff --git a/docs/src/main/paradox/release-notes/releases-1.1.md 
b/docs/src/main/paradox/release-notes/releases-1.1.md
index 0e6ba3ca..e07a7e86 100644
--- a/docs/src/main/paradox/release-notes/releases-1.1.md
+++ b/docs/src/main/paradox/release-notes/releases-1.1.md
@@ -1,13 +1,12 @@
 # Release Notes (1.1.x)
 
-## 1.1.0-M1
+## 1.1.0
 
-Release notes for Apache Pekko Connectors Kafka 1.1.0-M1.
-As with all milestone releases, this release is not recommended for production 
use - it is designed to allow users to try out the changes in a test 
environment.
+Release notes for Apache Pekko Connectors Kafka 1.1.0. This release is built 
with Apache Pekko 1.1. When upgrading to Apache Pekko Connectors Kafka 1.1.0, 
it is recommended that you also upgrade to use Apache Pekko 1.1.
 
 ### Dependency Changes
 
 Most of the dependency changes are small patch level upgrades. Some exceptions 
include:
 
-* kafka-clients 3.7.0
+* kafka-clients 3.8.0
 * slf4j was updated to v2


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

Reply via email to