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

fanningpj pushed a commit to branch 1.2.x
in repository https://gitbox.apache.org/repos/asf/pekko-persistence-jdbc.git


The following commit(s) were added to refs/heads/1.2.x by this push:
     new 56853e8  release notes for 1.2.0 (#390) (#408)
56853e8 is described below

commit 56853e8b2ce7352794c20a0ad9785b861d6f0b1a
Author: PJ Fanning <[email protected]>
AuthorDate: Sat Dec 20 09:37:34 2025 +0100

    release notes for 1.2.0 (#390) (#408)
    
    * release notes for 1.2.0
    
    * Update releases-1.2.md
    
    * Fix grammar and clarify upgrade instructions in release notes
    
    Corrected minor grammatical errors and clarified the text regarding 
database upgrades and new features.
    
    * Update migration.md
    
    * Update migration.md
    
    * Update releases-1.2.md
    
    * Update migration.md
---
 .github/workflows/publish-1.2-docs.yml             | 70 ++++++++++++++++++++++
 docs/src/main/paradox/migration.md                 |  9 ++-
 docs/src/main/paradox/release-notes/index.md       |  1 +
 .../src/main/paradox/release-notes/releases-1.2.md | 24 ++++++++
 4 files changed, 102 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/publish-1.2-docs.yml 
b/.github/workflows/publish-1.2-docs.yml
new file mode 100644
index 0000000..ebc8a3b
--- /dev/null
+++ b/.github/workflows/publish-1.2-docs.yml
@@ -0,0 +1,70 @@
+name: Publish 1.2 docs
+
+permissions:
+  contents: read
+
+on:
+  workflow_dispatch:
+
+jobs:
+  publish-docs:
+    # runs on main repo only
+    if: github.repository == 'apache/pekko-persistence-jdbc'
+    name: Publish
+    runs-on: ubuntu-22.04
+    env:
+      JAVA_OPTS: -Xms2G -Xmx2G -Xss2M -XX:ReservedCodeCacheSize=256M 
-Dfile.encoding=UTF-8
+    steps:
+      - name: Checkout
+        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # 
v5.0.0
+        with:
+          # we don't know what commit the last tag was it's safer to get 
entire repo so previousStableVersion resolves
+          fetch-depth: 0
+          fetch-tags: true
+          ref: 1.2.x
+
+      - name: Setup Java 8
+        uses: actions/setup-java@dded0888837ed1f317902acf8a20df0ad188d165 # 
v5.0.0
+        with:
+          distribution: temurin
+          java-version: 8
+
+      - name: Build Documentation
+        run: |-
+          sbt "set ThisBuild / version := \"1.2.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-persistence-jdbc/1.2.0/
+          mkdir -p target/nightly-docs/docs/pekko-persistence-jdbc/1.2/
+          cp -r docs/target/paradox/site/main/ 
target/nightly-docs/docs/pekko-persistence-jdbc/1.2.0/docs
+          cp -r docs/target/paradox/site/main/ 
target/nightly-docs/docs/pekko-persistence-jdbc/1.2/docs
+          rm -r docs/target/paradox/site/main/
+          cp -r target/scala-2.13/unidoc 
target/nightly-docs/docs/pekko-persistence-jdbc/1.2.0/api
+          cp -r target/scala-2.13/unidoc 
target/nightly-docs/docs/pekko-persistence-jdbc/1.2/api
+          rm -r target/scala-2.13/unidoc
+
+      - name: Upload 1.2.x docs
+        uses: ./.github/actions/sync-nightlies
+        with:
+          upload: true
+          switches: --archive --compress --update --delete --progress 
--relative
+          local_path: target/nightly-docs/./docs/pekko-persistence-jdbc/1.2.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 }}
+          remote_user: ${{ secrets.NIGHTLIES_RSYNC_USER }}
+          remote_key: ${{ secrets.NIGHTLIES_RSYNC_KEY }}
+
+      - name: Upload 1.2 docs
+        uses: ./.github/actions/sync-nightlies
+        with:
+          upload: true
+          switches: --archive --compress --update --delete --progress 
--relative
+          local_path: target/nightly-docs/./docs/pekko-persistence-jdbc/1.2 # 
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 }}
+          remote_user: ${{ secrets.NIGHTLIES_RSYNC_USER }}
+          remote_key: ${{ secrets.NIGHTLIES_RSYNC_KEY }}
diff --git a/docs/src/main/paradox/migration.md 
b/docs/src/main/paradox/migration.md
index 793f4af..300d0d9 100644
--- a/docs/src/main/paradox/migration.md
+++ b/docs/src/main/paradox/migration.md
@@ -1,4 +1,9 @@
-# Migration
+# Migration from Akka Persistence JDBC to Pekko Persistence JDBC 1.0.x/1.1.x
 
-* If you are looking to migrate from [Akka Persistence 
JDBC](https://doc.akka.io/docs/akka-persistence-jdbc/current/migration.html), 
you should upgrade to v5.1.x before attempting to migrate to Pekko's equivalent.
+* If you are looking to migrate from [Akka Persistence 
JDBC](https://doc.akka.io/docs/akka-persistence-jdbc/current/migration.html), 
you should upgrade to 5.1.x before attempting to migrate to Pekko's equivalent.
+* If you are using a newer version of Akka Persistence JDBC, it might be best 
to compare your table definitions with the Pekko table definitions of the 
version of Pekko Persistence JDBC that you intend to migrate to. It is possible 
that Akka have added changes that are not compatible with Pekko supports.
 * The [Pekko Migration 
Guide](https://pekko.apache.org/docs/pekko/1.0/project/migration-guides.html) 
is a good summary of the changes that you need to make when switching from Akka 
to Pekko.
+
+# Migrating to 1.2.x
+
+It is recommended that you read the section about DB Schema Changes in the 
@ref[1.2.0 Release Notes](release-notes/releases-1.2.md).
diff --git a/docs/src/main/paradox/release-notes/index.md 
b/docs/src/main/paradox/release-notes/index.md
index c81b99e..bd95457 100644
--- a/docs/src/main/paradox/release-notes/index.md
+++ b/docs/src/main/paradox/release-notes/index.md
@@ -4,6 +4,7 @@
 
 @@@ index
 
+* [1.2 Releases](releases-1.2.md)
 * [1.1 Releases](releases-1.1.md)
 * [1.0 Releases](releases-1.0.md)
 
diff --git a/docs/src/main/paradox/release-notes/releases-1.2.md 
b/docs/src/main/paradox/release-notes/releases-1.2.md
new file mode 100644
index 0000000..4541c2e
--- /dev/null
+++ b/docs/src/main/paradox/release-notes/releases-1.2.md
@@ -0,0 +1,24 @@
+# Release Notes (1.2.x)
+
+## 1.2.0
+
+Release notes for Apache Pekko Persistence JDBC 1.2.0. See [GitHub 
Milestone](https://github.com/apache/pekko-persistence-jdbc/milestone/6?closed=1)
 for a fuller list of changes.
+
+This release includes some changes from Akka Persistence JDBC 5.2.0, which 
have recently become available under the Apache License, Version 2.0.
+
+### Schema Changes
+
+If you have a pre-existing Pekko Persistence JDBC database and want to upgrade 
to 1.2.0, it is encouraged for you to update the table definitions. This is not 
done automatically. We do not expect that there will be issues if you don't 
update the table definitions (unless you try to use new features like Durable 
State support for MySQL and MariaDB).
+
+Please take care when updating the table definitions. We would recommend 
backing up your database first and ideally, trying the whole process in a test 
environment before approaching your production database.
+
+For users migrating from older releases, there are some migration scripts that 
we provide but you need to apply them yourself. They can be found in our [git 
repo](https://github.com/apache/pekko-persistence-jdbc/tree/1.2.x/core/src/main/resources/schema)
 or the source release. The `migration-1.2.0` directories can be found for some 
of the database types that we support. MariaDB users should use the 
`mariadb/migration-1.2.0` instead of the `mysql` one. Please test the scripts 
using a test [...]
+
+* Change Oracle DELETED column type from CHAR to NUMBER 
([PR323](https://github.com/apache/pekko-persistence-jdbc/pull/323))
+* Add MariaDB schema support. Pre-existing users can stick with using the 
MySQL dialect that we already supported. The explicit MariaDB support allows 
use of Durable State persistence that works well in MariaDB but that relies on 
a feature not availabe in MySQL 
([PR367](https://github.com/apache/pekko-persistence-jdbc/pull/367))
+* Implement Durable State handling with MySQL. MariaDB users should prefer the 
specific MariaDB solution in PR367. 
([PR378](https://github.com/apache/pekko-persistence-jdbc/pull/378))
+* use NVARCHAR instead of VARCHAR for SQL Server 
([PR382](https://github.com/apache/pekko-persistence-jdbc/pull/382))
+
+### Changes
+
+* Limit events by tag query ordering sizes 
([PR381](https://github.com/apache/pekko-persistence-jdbc/pull/381))


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

Reply via email to