On behalf of the community I’m pleased to announce the release of Spring Session 2.0.0.RC1. This release puts some final touches to preparing for 2.0.0.RELEASE. You can find the complete changelog in github, with the highlights below:

• #906 Simplified integration with the Servlet APIs. With this simplification, we have removed the support for supporting multiple sessions for a single user. We plan on looking into other ways to bring this feature back.

• #907 Support for configuring Redis session cleanup cron

Project Site | Reference | Help

On behalf of the Spring Integration team I am pleased to announce that the Release Candidate 1 for the Spring Integration 5.0 version (5.0.0.RC1) is now available.

It can be downloaded from the Milestone Repository:

repositories {
    maven { url 'http://repo.spring.io/libs-milestone' }
}

compile "org.springframework.integration:spring-integration-core:5.0.0.RC1"

20 JIRAs (and some GitHub issues) are included in this release, together with bug fixes and a number of new features. Some highlights of features in the RC1, since the previously announced Milestone 7:

• The components populated by the Java DSL parser are now registered as BeanDefinitions in the application context, thanks to newly introduced in the Spring Framework 5.0 Supplier-based programmatic bean registration. This approach helps us to avoid some boilerplate code for singletons registration and initialization. In addition this BeanDefinition registration may be useful in some use-case to select particular components in the application context. In fact, exactly that is used in the Spring Cloud Function project for java.util.function.* beans scanning.

• The IntegrationFlows.from(Class<?> serviceInterface) has now overloaded version with an additional beanName argument. This becomes exactly the bean name for a generates gateway proxy overriding the [flowId].gateway value:

  @Bean public IntegrationFlow uppercaseFlow() { return IntegrationFlows.from(MessageFunction.class, "uppercase") .<String, String>transform(String::toUpperCase) .get(); }

  …

On behalf of the Spring Cloud team, it is my pleasure to announce a new milestone release of Spring Cloud Pipelines - 1.0.0.M7.

What’s new?

This release adds a lot of new features and quality and testing improvements. As for main features, we’ve added Kubernetes support for Jenkins and Concourse. As for quality and testing, we’ve written over 150 Bash tests, added Shellcheck, EditorConfig and written more Jenkins tests. We’ve also unified the project’s documentation that now can be available for each milestone under Spring Cloud Static gh-pages. The docs for 1.0.0.M7 are available here - http…

On behalf of the community, I am pleased to announce that the Milestone 3 (M3) of the Spring Cloud Finchley Release Train is available today. The release can be found in Spring Milestone repository. You can check out the Finchley release notes for more information.

Notable Changes in the Finchley Release Train

A common theme among many of the projects included in the Finchley release train is adding support for WebFlux, WebClient, Micrometer or other integrations within the Spring Reactive theme.

Spring Cloud Sleuth

WebFlux and Reactor are supported again. OAuth support is not included. The spring-cloud-sleuth-zipkin-stream…

On behalf of everyone who contributed, it's my pleasure to announce that Spring REST Docs 2.0.0.RC1 has been released and is available from https://repo.spring.io/milestone/.

What's new?

Spring REST Docs 2.0 is the latest generation of the project and requires Spring Framework 5.0 and Java 8.

The main highlight of the 2.0 release is support for using Spring WebFlux's WebTestClient to document an API. WebTestClient can be used for lightweight testing and documentation of APIs implemented using WebFlux Fn and WebFlux's annotation-based programming model. It can also be used to document any API…

On behalf of the team, I am pleased to announce the release of Spring Cloud Skipper 1.0 M1.

Skipper is a lightweight tool that allows you to discover Spring Boot applications and manage their lifecycle on multiple Cloud Platforms. You can use Skipper standalone or integrate it with Continuous Integration pipelines to help implement the practice of Continuous Deployment.

The main features in Skipper 1.0 M1 are:

• Define multiple platform accounts where Spring Boot applications can be deployed. Supported platforms are Local, Cloud Foundry, and Kubernetes.
• Substitute variables in Mustache templated files that describe how to deploy applications to a platform.
• Search Package Repositories for existing applications.
• Upgrade/Rollback a package based on a simple blue/green workflow.
• Store the history of resolved template files (aka 'application manifests') which represent the final description of what has been deployed to a platform for a specific release.
• Use via a standalone interactive shell or web API.
…

A shipment of fixes and goodies has arrived and it is brought to you by the new Bismuth-SR3 Bill Of Material. This version is now used by Spring Framework 5.0.1 ! Our site projectreactor.io reflects those latest updates.

Reactor-Core 3.1.1

release notes

A quality update including more than 20 fixes and just a couple new features: Kotlin extensions for Reactor conversion from Publisher and the Flux#limitRequest operator alternative to Flux#take with an explicit upper limit to the produced demand.

We are now working on 3.1.2.RELEASE. Have a look at our issues backlog for a more detailed scope.

…

On behalf of the community, I am pleased to announce that the Release Candidate 1 (RC1) of the Spring Cloud Edgware Release Train is available today. The release can be found in Spring Milestone repository. You can check out the Edgware release notes for more information.

Notable Changes in the Edgware Release Train

Renamed starters

A number of starters did not follow normal Spring Cloud naming conventions. In Edgware, use of the deprecated starter will log a warning with the name of the new starter to use in its place. Below is a table of the deprecated starters and their replacements

Dear Spring community,

It is my pleasure to announce that Spring Framework 5.0.1 is available now, as the first maintenance release in our Spring Framework 5.0 line.

In addition to addressing various user-reported bugs, we've applied minor refactorings to clean up unintended leftovers from the 5.0 GA release, e.g. for the reactive codec configurers.

This release upgrades Reactor to Bismuth SR3, based on Reactor Core 3.1.1, picking up essential fixes in Reactor Netty. Furthermore, AspectJ 1.8.12 brings some welcome performance improvements to Spring AOP's pointcut expression evaluation at…