On behalf of the Spring Batch team, I am pleased to announce that Spring Batch 4.3.0-M2 is now available from our milestone repository.

What’s new?

This release comes with a number of new features and enhancements that you can find in the release notes, but here are the major highlights:

1. Kafka support enhancements

By default, the KafkaItemReader reads a topic from the beginning. When we initially introduced this reader in v4.2, it was not possible to configure it to read records from a custom offset. In this release, we added this feature. As a result of this addition, it is now possible to…

Dear Spring community,

On behalf of the team and everyone who contributed, it is my pleasure to announce the second milestone for Spring Integration 5.4 generation.

It can be downloaded from our milestone repository:

compile 'org.springframework.integration:spring-integration-core:5.4.0-M2'

This version continues a story since milestone 1 for aggressive dependencies upgrades and deprecation removals, including legacy metrics.

Some key highlights in this milestone alongside with the number of bugfixes and refactorings:

• The fix for CVE-2020-5413;

• An Inbound Channel Adapter for R2DBC;

• A Reactive Message Producer implementation for Redis Stream;

• A ZeroMqChannel is implemented, too;

• The RMI module is deprecated now.

…

On behalf of the community, I’m pleased to announce the release of Spring Security 5.3.4 (release notes), 5.2.6 (release notes), 5.1.12 (release notes) , 5.0.18 (release notes), 4.2.18 (release notes). These releases deliver bug fixes along with some minor improvements. Users are encouraged to update to the latest patch release.

Project Site | Reference | Help

On behalf of the Spring Data team, I’m pleased to announce the availability of the third service release of the Spring Data Neumann release train. Neumann SR3 ships with 34 tickets fixed.

This release ships with mostly bug fixes and dependency upgrades and will be picked up by Spring Boot 2.3.3 in the coming days.

Here are the detailed links to each individual artifact and the reference documentation:

• Spring Data Commons 2.3.3 - Artifacts - Javadoc - Documentation - Changelog
• Spring Data JDBC 2.0.3 - Artifacts - Javadoc - Documentation - Changelog
• Spring Data JPA 2.3.3 - Artifacts - Javadoc - Documentation - Changelog
• Spring Data KeyValue 2.3.3 - Artifacts - Javadoc - Documentation - Changelog
• Spring Data for Apache Cassandra 3.0.3 - Artifacts - Javadoc - Documentation - Changelog
• Spring Data for Apache Solr 4.2.3 - Artifacts - Javadoc - Documentation - Changelog
• Spring Data Neo4j 5.3.3 - Artifacts - Javadoc - Documentation - Changelog
• Spring Data for Apache Geode 2.3.3 - Artifacts - Javadoc - Documentation - …

On behalf of the Spring Data team I’m delighted to announce the second milestone of the 2020.0.0 release train (codename "Ockham"). This release ships almost 120 tickets fixed! The most important new features are:

• Support for reactive SpEL context extensions.
• Support for reactive auditing in Cassandra, Elasticsearch, MongoDB, and R2DBC.
• Integration of Spring Data Neo4j 6.0, which is a rewrite of the module without relying on Neo4j OGM.
• Refactoring of Spring Data R2DBC on top of Spring Framework's R2DBC module.
• Oracle dialect for Spring Data JDBC.

Find a curated changelog in our release train wiki or skim through a full list of changes in JIRA. Next up is 2020.0.0-RC1 planned for mid-September…

On behalf of the team and everyone who has contributed, I am pleased to announce that Spring Framework 5.3.0-M2 is available now.

The second milestone of Spring Framework 5.3 includes 55 fixes and improvements.

If you want to give the milestone a try, you can bootstrap a new application on start.spring.io once Spring Boot 2.4.0-M2 is released later this week.

Project Page | GitHub | Issues | Documentation

On behalf of the community, I am pleased to announce that Service Release 7 (SR7) of the Spring Cloud Hoxton Release Train is available today. The release can be found in Maven Central. You can check out the Hoxton release notes for more information.

Notable Changes in the Hoxton Release Train

See all of the included issues and pull requests at the GitHub project.

Spring Cloud Netflix

CVE-2020-5412: Hystrix Dashboard Proxy In spring-cloud-netflix-hystrix-dashboard

Spring Cloud Cloud Foundry

Upgraded CF Java client to 3.25.0.RELEASE.

Spring Cloud Consul

Added support for byte[] messages in…

Spring Cloud Data Flow team is pleased to announce the release of 2.6.0.

This 2.6.0 adds usual bug fixes and the following key highlights:

• Wavefront New integration to monitor streams and tasks using Wavefront. More about this feature can be found from Stream Monitoring and Task Monitoring

• Platform Support for Scheduling Tasks scheduling now have a platform support. See Scheduling Tasks

• Java CFEnv We're now on a new version of Java CFEnv which greatly improves user experience when there is a need to bind to user created services.

• Bitnami We've moved from a Helm Hub to Bitnami as a helm chart storage.

• Composed Task Runner as SCDF native module Composed Task Runner is now an integral part of SCDF itself and gets registered implicitly while the users who have the custom composed task runner can still override the native one. This enables us to integrate the composed tasks management within the context of Spring Cloud Data Flow.

  …

Dear Spring community,

Spring HATEOAS 1.1.1.RELEASE is out, the first patched release of the latest stable line, supporting Spring Boot 2.3.

Among many things, you’ll find:

• We are now listing community-led efforts to implement other media types. JSON:API and Siren are the latest. You want to add another media type? Just check out the details.

• VndErrors is a media type for reporting, well, errors. And it has had a sneaky bug that crept in that we’ve now patched. "logref" values are no longer confined to integers. It’s important to also note that the VndErrors spec is showing no signs of life, hence we’ve deprecated its support. If you’re starting a new hypermedia-driven project, our recommendation is to use RFC-7807’s application/problem+json format instead. The API is more elegant and more importantly, under active development. And we’ve made some fixes based on community feedback.

  …