Release 0.5.0

[scordio]

Hi @mchmielarz and @pivovarit, a user on BlueSky asked when the 0.5.0 release for assertj-vavr will happen.

Any new release under the AssertJ namespace will need to be done via the Sonatype Central Publisher Portal. We haven't migrated the core modules yet, but we plan to do that soon (assertj/assertj#3822). However, we had in mind to target the new major version only, which will also push you to increase the language level to 17.

In case you plan to continue targeting Java 8, I'd be happy to consider releasing a new AssertJ Parent POM 3.27 patch version, which would bring the building blocks of the Central Publisher Portal so that you could use them in this project.

Would that make sense?

[pivovarit]

Vavr will also soon bump the language level up, so it won't be an issue. However, keep in mind that all artifacts will need to be released via Central Portal. You can't do that for the new major version release, but also for everything along the way.

I have gone through this exercise myself and can help you out if needed:

• https://github.com/pivovarit/maven-central-example

[scordio]

You can't do that for the new major version release, but also for everything along the way.

I meant that parent 2.2.18 is currently in use in assertj-vavr.

You could upgrade to 3.27.3 but the parent would still provide the nexus-staging-maven-plugin under the hood, and so far we didn't plan any new 3.27 release.

The options I see for assertj-vavr are:

• Stay on the current parent version or upgrade to 3.27.3, dealing with the release setup on your own.
• Wait for parent version 4, which will support the Central Portal natively, but it will take some time before we release a GA version (likely, months).
• We plan a 3.27.4 release for the parent, which will bring support for the Central Portal and would give more freedom to external modules like assertj-vavr.

In case you'd like us to go after the last option, just let me know 🙂