+1 for this change/release. Note 1.2.0 didn't really break binary compatibility as defined in https://pekko.apache.org/docs/pekko/current/common/binary-compatibility-rules.html, since https://github.com/apache/pekko/pull/1940/files only removed an internal method, which should be safe. The 'fault' was in pekko-persistence-cassandra, which apparently relied on this internal method without making sure it was marked @InternalStableApi ( https://github.com/apache/pekko/blob/main/actor/src/main/java/org/apache/pekko/annotation/InternalStableApi.java). Of course, this is water under the bridge, and while Pekko Core was not 'at fault', fixing the issue with Pekko Core 1.2.1 is a practical solution.
On Wed, Sep 17, 2025 at 9:38 PM PJ Fanning <[email protected]> wrote: > Hi everyone, > There was a binary compatibility issue reported about 1.2.0 that > affects pekko-persistence-cassandra users. > https://github.com/apache/pekko/pull/2195 > > The full milestone is at: > https://github.com/apache/pekko/milestone/20?closed=1 > > There is one open PR and if there are no objections to it, I will > merge it in the next few days. > https://github.com/apache/pekko/pull/2219 > > I can act as release manager if there are no objections to proceeding > with a release. If anyone else wants to release manage, please let us > know. > > Thanks, > PJ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Arnout Engelen ASF Security Response Apache Pekko PMC member, ASF Member NixOS Committer Independent Open Source consultant
