It is my pleasure to announce that Spring Boot 1.4.5 and 1.5.2 have been released and are available now from repo.spring.io and Maven Central.

Spring Boot 1.4.5 includes 50 fixes and a selection of improvements and dependency upgrades. The second (first, really!) maintenance release of the 1.5 line contains over 60 fixes, improvements and 3rd party dependency updates. Thanks to all that have contributed!

What's next?

The team is now working full speed on Spring Boot 2: a first milestone, including the first release candidate of Spring Framework 5, is expected early April. There are quite a lot of reactive-related features already in 2.0 snapshots. If you’d like to try them out, and we’d love to hear your feedback if you do, please go to start.spring.io…

On behalf of the community, I’m pleased to announce the release of Spring Security 4.2.2 which fix has a number of bug fixes. Users are encouraged to update immediately.

Project Site | Reference | Guides | Help

On behalf of the entire team, I'd like to announce the availability of Ingalls SR1 and Hopper SR8 service releases. Both of them ship 77 issues fixed in total. As usual, service releases are bugfix ones and recommended upgrades for all users. The releases are going to be picked up by the upcoming Boot 1.5 and 1.4 services releases for your convenience.

The complete list of issues fixed for Ingalls SR1 can be found here, the one for Hopper SR 8 here.

Spring Data Ingalls SR1

• Spring Data Commons 1.13.1 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data JPA 1.11.1 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data KeyValue 1.2.1 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data for Apache Cassandra 1.5.1 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data for Apache Solr 2.1.1 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Gemfire 1.9.1 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Neo4j 4.2.1 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data MongoDB 1.10.1 - Artifacts - JavaDocs - Documentation - …

It is my pleasure to announce that Spring Framework 4.3.7 has been released.

This maintenance release is the base for the upcoming Spring Boot 1.4.5 and 1.5.2 releases and includes over 20 fixes and selected improvements.

Project Page | GitHub | Issues | Documentation

Dear Spring community,

Leading into 2017, the fifth Spring Framework 5.0 milestone is available now. Once again, please check the project page for how to obtain it from our milestone repository.

This is the last milestone before we enter the release candidate phase. Our feature-complete RC1 is planned for early April, initiating a series of release candidates up until June. With this timeline, against near-final releases of OpenJDK 9 and several EE 8 specifications, our 5.0 generation covers early JDK 9 support as well as Servlet 4.0 and Bean Validation 2.0 already.

On another front, 5.0 M5 finally introduces a dedicated name for our reactive web framework: It is my pleasure to publicly announce Spring WebFlux, with the spring-web-reactive module renamed to spring-webflux…

A batch update of releases has arrived and it is brought to you with the new Aluminium-SR1 Bill Of Material. Just in time for Spring Framework M5 !

Reactor-Core 3.0.5

release notes

An important quality update with new features including predicated-based windows and the checkpoint operator, fixes, test coverage and for the first time in 3.0.x line, a draft reference guide.

We are now working on 3.0.6.RELEASE which is going to be our last major 3.0 content update before 3.1.0.RELEASE. We encourage our Spring Community to just follow deprecated instructions if they hit any of the @Deprecated API, thus simply preparing for a quick, painless, upgrade when time comes. Have a look at our issues backlog…

The 1.1.1.RELEASE maintenance release of Spring Cloud Data Flow for Cloud Foundry is now available and includes a variety of stability and performance improvements. Following are the highlights:

• Stability Improvements The instability problems when using SCDF’s 1.1.0.RELEASE on PCF manifested to the users in the following forms.

  • stream list operation would hang and eventually time out with “IllegalStateException: 503 Bad Gateway” or “IllegalStateException: Timeout on block read” exceptions. This is addressed in the cf-java-client library.

  • With SCDF server sitting cold/idle for a period of time and with OAUTH token refresh routine happening in the background, any new operation to the server would never complete. The OAUTH refresh token routine had a bug in successfully negotiating for new tokens. This is addressed in the cf-java-client library.

  …

It's my pleasure to announce that Spring IO Platform Brussels-RELEASE is available now from the Spring release repository and Maven Central.

The Brussels release introduces the following projects to the Platform:

• Spring Kafka 1.1

The Brussels release also upgrades the versions of a number of projects:

• Spring AMQP 1.7
• Spring Boot 1.5
• Spring Data Ingalls
• Spring Integration Java DSL 1.2
• Spring Integration Kafka 2.1
• Spring LDAP 2.3
• Spring Security 4.2
• Spring Session 1.3
• Spring Web Services 2.4

The versions of numerous third-party dependencies have also been updated.

Project Page | GitHub | Issues | …

On behalf of the team, I am excited to announce the release of the first milestone of Spring Cloud Data Flow 1.2.

Note: A great way to start using this new release(s) is to follow the release matrix on the project page, which includes the download coordinates and the links to the reference guide.

Over the last few weeks, we have added new features and improvements to the overall orchestration of data microservices. The following new features were included in the 1.2.0.M1 release:

Core

• Introduce dedicated prefixes for deployment properties. Using the deployer properties is as simple as deployer.<appname>.xxx as opposed to app.<appname>.spring.cloud.deployer.xxx
• Introduce a new REST-API controller and shell support to cleanup Task Executions
• Foundation work to consolidate the use of controllers between Task deployments and Task Executions
• Consolidate REST-API call traces and return codes for consistency
• Adds role-based access control to define who has access to create, deploy, destroy, or view streams/tasks. This works seamlessly in coordination with the supported authentication methods…