Some of the changes in Pekko Persistence R2DBC 1.1.0 rely on changes
in Pekko Core that were added in 1.1.3. I think it is a little untidy
to depend on 1.1.3 and since Pekko Core 1.2.0 is now released, we can
change the dependency version in Pekko Persistence R2DBC.
I don't think that we should generally start making special releases
for our other modules. It is expected that any app or lib that works
with Pekko Core 1.1.x should work with Pekko Core 1.2.x without any
issues.

On Mon, 1 Sept 2025 at 12:42, kerr <hepin1...@gmail.com> wrote:
>
> +1, and then it seems we can let the main depend on Pekko 1.2.x?
>
> 何品
>
>
> PJ Fanning <fannin...@apache.org> 于2025年9月1日周一 19:37写道:
>
> > Hi everyone,
> > This is the last repo where we don't yet have a 1.1.0 release.
> > I think this is a good time to get this released.
> >
> > Release Notes
> >
> > https://github.com/apache/pekko-persistence-r2dbc/blob/f0062d3d150536541485b8a03f48970421a5aa0a/docs/src/main/paradox/release-notes/releases-1.1.md
> >
> > I can act as release manager but if anyone else wants to take on the
> > role, please let us know.
> >
> > What does everyone think?
> >
> > Thanks,
> > PJ
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org
> > For additional commands, e-mail: dev-h...@pekko.apache.org
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org
For additional commands, e-mail: dev-h...@pekko.apache.org

Reply via email to