Recently JBeret has a major version release::

In this release it include these major changes:

And it added the tests against main branch of WildFly server, both preview and non-preview ones:

In addition, it removes some unnecessary API dependencies:

And it contains these Jakarta API related components upgrades:

It’s worth mentioning these component upgrades were done in preparation for Jakarta EE 11. While they should be mostly backwards compatible, you should verify against your application given there is a potential for API breakage.

In addition, when the JBeret is used in an integrated environment, such as the batch-jberet module inside the WildFly, it will inherit the annotation-api and cdi-api versions used by WildFly itself. So this is a difference between JBeret SE and JBeret used inside an integrated environment like WildFly.

At last, there are relative tasks related with the Batch TCK testings that are done during the phase of this release:

The above is the information of the 3.0.0.Beta1 release.