v1.1.0 release notes

.github/workflows/publish-1.1-docs.yml

@@ -26,17 +26,17 @@ 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"
 
       # 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/1.1.0-M1/
+          mkdir -p target/nightly-docs/docs/pekko-connectors/1.1.0/
           mkdir -p target/nightly-docs/docs/pekko-connectors/1.1/
-          cp -r docs/target/paradox/site/main/ target/nightly-docs/docs/pekko-connectors/1.1.0-M1/docs
+          cp -r docs/target/paradox/site/main/ target/nightly-docs/docs/pekko-connectors/1.1.0/docs
           cp -r docs/target/paradox/site/main/ target/nightly-docs/docs/pekko-connectors/1.1/docs
           rm -r docs/target/paradox/site/main/
-          cp -r target/scala-2.13/unidoc target/nightly-docs/docs/pekko-connectors/1.1.0-M1/api
+          cp -r target/scala-2.13/unidoc target/nightly-docs/docs/pekko-connectors/1.1.0/api
           cp -r target/scala-2.13/unidoc target/nightly-docs/docs/pekko-connectors/1.1/api
           rm -r target/scala-2.13/unidoc
 
@@ -45,7 +45,7 @@ jobs:
         with:
           upload: true
           switches: --archive --compress --update --delete --progress --relative
-          local_path: target/nightly-docs/./docs/pekko-connectors/1.1.0-M1 # The intermediate dot is to show `--relative` which paths to operate on
+          local_path: target/nightly-docs/./docs/pekko-connectors/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 }}

docs/src/main/paradox/release-notes/releases-1.1.md

@@ -1,9 +1,8 @@
 # Release Notes (1.1.x)
 
-## 1.1.0-M1
+## 1.1.0
 
-Release notes for Apache Pekko Connectors 1.1.0-M1. See [GitHub Milestone](https://github.com/apache/pekko-connectors/milestone/2?closed=1) for a fuller list of changes.
-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 1.1.0. See [GitHub Milestone for 1.1.0-M1](https://github.com/apache/pekko-connectors/milestone/2?closed=1) and [GitHub Milestone for 1.1.0](https://github.com/apache/pekko-connectors/milestone/7?closed=1) for a fuller list of changes.
 
 ### Known Issues
 
@@ -14,17 +13,19 @@ The most notable issues are with:
 * HBase ([#61](https://github.com/apache/pekko-connectors/issues/61))
 * IronMQ ([#697](https://github.com/apache/pekko-connectors/issues/697))
 
-With OrientDB Connector, it appears that the latest orientdb client only works with OrientDB 3.2 servers. If you use an older version of OrientDB, you may be better off sticking the Pekko Connectors 1.0.x ([PR361](https://github.com/apache/pekko-connectors/pull/361)).
+With OrientDB Connector, it appears that the latest OrientDB client only works with OrientDB 3.2 servers. If you use an older version of OrientDB, you may be better off sticking with Pekko Connectors 1.0.x ([PR361](https://github.com/apache/pekko-connectors/pull/361)).
 
 ### Fixes
 
 * Close JMS sessions when exceptions happen ([PR485](https://github.com/apache/pekko-connectors/pull/485)).
+* SQS: delaySeconds parameter is not populated in SendMessageBatchRequestEntry ([#759](https://github.com/apache/pekko-connectors/issues/759)). (not in v1.1.0-M1)
 
 ### Additions
-* Scala 3 is now support for the Slick Connector.
+* Scala 3 is now supported for the Slick Connector.
 * New connector `couchbase3` that uses Couchbase Client v3. The pre-existing `couchbase` connector still uses the older v2 Client.
 * New connector `jakartams` which is the [Jakarta Messaging](https://jakarta.ee/learn/docs/jakartaee-tutorial/current/messaging/jms-concepts/jms-concepts.html) equivalent of the JMS connector.
 * `aws-spi-pekko-http` is now part of Apache Pekko, as opposed to being an externally maintained lib.
+* aws-spi-pekko-http: Allow using SdkHttpConfigurationOption over default pekko-http connection settings ([PR827](https://github.com/apache/pekko-connectors/pull/827)). (not in v1.1.0-M1)
 * New pekko-connectors-bom ([PR633](https://github.com/apache/pekko-connectors/pull/633)).
 
 ### Changes
@@ -34,10 +35,11 @@ With OrientDB Connector, it appears that the latest orientdb client only works w
 * Google Common: Use scope config for compute-engine auth ([PR313](https://github.com/apache/pekko-connectors/pull/313)).
 * Google Common: Remove duplicate scopes value in reference.conf ([PR314](https://github.com/apache/pekko-connectors/pull/314)).
 * New config for AMQP Connector that allows you to improve performance by reusing byte arrays ([PR592](https://github.com/apache/pekko-connectors/pull/592)).
+* Google Common: Improve error message in case of response failure ([PR799](https://github.com/apache/pekko-connectors/pull/799)). (not in v1.1.0-M1)
 
 ### Dependency Upgrades
 
-Most dependencies have been upgraded to the latest available version that still supports Java 8 as of release time.
+Most dependencies have been upgraded to the latest available version that still supports Java 8 as of release time (October 2024).
 Exceptions include:
 
 * HBase (see Known Issues above)