You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pekko.apache.org by PJ Fanning <fa...@apache.org> on 2025/09/17 19:38:00 UTC

[DISCUSS] Pekko (Core) 1.2.1 release?

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: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org


Re: [DISCUSS] Pekko (Core) 1.2.1 release?

Posted by kerr <he...@gmail.com>.
+1
何品


PJ Fanning <fa...@apache.org> 于2025年9月18日周四 03:38写道:

> 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: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>

Re: [DISCUSS] Pekko (Core) 1.2.1 release?

Posted by Arnout Engelen <en...@apache.org>.
+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 <fa...@apache.org> 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: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>

-- 
Arnout Engelen
ASF Security Response
Apache Pekko PMC member, ASF Member
NixOS Committer
Independent Open Source consultant