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

github-bot pushed a change to branch update/jackson-core-2.16.0
in repository https://gitbox.apache.org/repos/asf/incubator-pekko.git


    omit 70753c43cd Update jackson-core to 2.16.0
     add 38324fc1a6 Update lmdbjava to 0.9.0 (#840)
     add 81ff45c301 Update metrics-core, metrics-jvm to 4.2.23 (#839)
     add d8943ce391 support reading akka-persistence snapshots (#837) (#838)
     add 7332626430 Use recoverWith instead of recover in SnapshotSerializer 
akka backwards compatibility (#841) (#843)
     add cc8bf7671b try to fix ClusterActorLoggingSpec (#808)
     add cc82462093 Update jackson-core to 2.16.0

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   (70753c43cd)
            \
             N -- N -- N   refs/heads/update/jackson-core-2.16.0 (cc82462093)

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:
 .../cluster/typed/ClusterActorLoggingSpec.scala    |  1 +
 .../serialization/SnapshotSerializer.scala         | 10 ++++-
 .../serialization/SnapshotSerializerSpec.scala     | 45 ++++++++++++++++++++++
 project/Dependencies.scala                         |  6 +--
 4 files changed, 58 insertions(+), 4 deletions(-)
 create mode 100644 
persistence/src/test/scala/org/apache/pekko/persistence/serialization/SnapshotSerializerSpec.scala


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

Reply via email to