You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pekko.apache.org by fa...@apache.org on 2025/09/10 10:30:46 UTC

(pekko-persistence-r2dbc) branch main updated: Revise release notes for Apache Pekko Persistence R2DBC 1.1.0 (#235)

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-persistence-r2dbc.git


The following commit(s) were added to refs/heads/main by this push:
     new f7514bb  Revise release notes for Apache Pekko Persistence R2DBC 1.1.0 (#235)
f7514bb is described below

commit f7514bb57428304963fdf3cfa17bfce98dd89015
Author: PJ Fanning <pj...@users.noreply.github.com>
AuthorDate: Wed Sep 10 11:30:41 2025 +0100

    Revise release notes for Apache Pekko Persistence R2DBC 1.1.0 (#235)
    
    * Revise release notes for Apache Pekko Persistence R2DBC 1.1.0
    
    Updated release notes for version 1.1.0, including breaking changes and dependency updates.
    
    * Revise breaking changes for Postgres and MySQL dependencies
    
    * Clarify Postgres and MySQL support in release notes
    
    * Update publish-1.1-docs.yml
---
 .github/workflows/publish-1.1-docs.yml              | 10 +++++-----
 docs/src/main/paradox/release-notes/releases-1.1.md | 17 +++++++++++------
 2 files changed, 16 insertions(+), 11 deletions(-)

diff --git a/.github/workflows/publish-1.1-docs.yml b/.github/workflows/publish-1.1-docs.yml
index 76446a3..7ef1a73 100644
--- a/.github/workflows/publish-1.1-docs.yml
+++ b/.github/workflows/publish-1.1-docs.yml
@@ -33,17 +33,17 @@ jobs:
 
       - name: Build 1.1.x 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 1.1.x directory structure
         run: |-
-          mkdir -p target/nightly-docs/docs/pekko-persistence-r2dbc/1.1.0-M1/
+          mkdir -p target/nightly-docs/docs/pekko-persistence-r2dbc/1.1.0/
           mkdir -p target/nightly-docs/docs/pekko-persistence-r2dbc/1.1/
-          cp -r docs/target/paradox/site/main/ target/nightly-docs/docs/pekko-persistence-r2dbc/1.1.0-M1/docs
+          cp -r docs/target/paradox/site/main/ target/nightly-docs/docs/pekko-persistence-r2dbc/1.1.0/docs
           cp -r docs/target/paradox/site/main/ target/nightly-docs/docs/pekko-persistence-r2dbc/1.1/docs
           rm -r docs/target/paradox/site/main/
-          cp -r docs/target/scala-2.13/unidoc target/nightly-docs/docs/pekko-persistence-r2dbc/1.1.0-M1/api
+          cp -r docs/target/scala-2.13/unidoc target/nightly-docs/docs/pekko-persistence-r2dbc/1.1.0/api
           cp -r docs/target/scala-2.13/unidoc target/nightly-docs/docs/pekko-persistence-r2dbc/1.1/api
           rm -r docs/target/scala-2.13/unidoc
 
@@ -52,7 +52,7 @@ jobs:
         with:
           upload: true
           switches: --archive --compress --update --delete --progress --relative
-          local_path: target/nightly-docs/./docs/pekko-persistence-r2dbc/1.1.0-M1 # The intermediate dot is to show `--relative` which paths to operate on
+          local_path: target/nightly-docs/./docs/pekko-persistence-r2dbc/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 a7e6ea8..cadaca6 100644
--- a/docs/src/main/paradox/release-notes/releases-1.1.md
+++ b/docs/src/main/paradox/release-notes/releases-1.1.md
@@ -2,24 +2,29 @@
 
 Apache Pekko Persistence R2DBC 1.1.x releases support Java 8 and above.
 
-## 1.1.0-M1
+## 1.1.0
 
-Release notes for Apache Pekko Persistence R2DBC 1.1.0-M1. See [GitHub Milestone for 1.1.0-M1](https://github.com/apache/pekko-persistence-r2dbc/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 Persistence R2DBC 1.1.0. See [GitHub Milestone for 1.1.0-M1](https://github.com/apache/pekko-persistence-r2dbc/milestone/2?closed=1) and [GitHub Milestone for 1.1.0](https://github.com/apache/pekko-persistence-r2dbc/milestone/3?closed=1) for a fuller list of changes.
 
 ### Breaking Changes
 
 * The dependency on org.postgresql:r2dbc-postgresql is no longer added to our dependency pom.xml
-    * Users need to add their own explicit dependency if they want to use Postgres (version 1.0.7.RELEASE recommended)
-    * We now support Postgres and MySQL in pekko-persistence-r2dbc and pekko-projection-r2dbc
-    * MySQL users will need to add their own explicit dependency on io.asyncer:r2dbc-mysql (version 1.3.0 recommended) ([PR175](https://github.com/apache/pekko-persistence-r2dbc/pull/175), [PR177](https://github.com/apache/pekko-persistence-r2dbc/pull/177))
+    * Users need to add their own explicit dependency if they want to use Postgres (release tested with r2dbc-postgresql 1.0.7.RELEASE)
+    * We now also support MySQL (see below), so we think it is tidier to make the Postgres and MySQL dependencies optional
 * change R2dbcExecutor functions that work with getRowsUpdated to return Future[Long] ([PR90](https://github.com/apache/pekko-persistence-r2dbc/pull/90))
 * Durable State: support revision in deletes ([PR92](https://github.com/apache/pekko-persistence-r2dbc/pull/92))
+* Configuring persistence plugins at runtime ([PR194](https://github.com/apache/pekko-persistence-r2dbc/pull/194))
+    * We removed implicit merging of specific plugin configuration (`pekko.persistence.r2dbc.journal`, `pekko.persistence.r2dbc.snapshot`, etc.) with shared configuration (`pekko.persistence.r2dbc`) upon plugin initialization, which means that specific plugin configurations must refer to shared keys explicitly.
+    * Users with relatively simple configurations for their applications - ones that more or less adhere to reference configuration structure and are merged with reference configuration (by using, for example, `ConfigFactory.load`) - should be able to migrate without additional changes to configuration.
+        * Merging with reference configuration adds explicit shared key references.
 
 ### Changes
 
+* We now support Postgres and MySQL in pekko-persistence-r2dbc and pekko-projection-r2dbc
+    * MySQL users will need to add their own explicit dependency on io.asyncer:r2dbc-mysql (release tested with r2dbc-mysql 1.4.1) ([PR175](https://github.com/apache/pekko-persistence-r2dbc/pull/175), [PR177](https://github.com/apache/pekko-persistence-r2dbc/pull/177))
 * Add ConnectionFactoryOptionsCustomizer ([PR171](https://github.com/apache/pekko-persistence-r2dbc/pull/171))
 
 ### Dependency Changes
 
 * upgrade io.r2dbc dependencies to 1.0.x
+* upgraded JDBC driver dependencies used in tests


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