The Spring Blog

Engineering
Releases
News and Events

Spring Security 5.3.0.M1 Released

On behalf of the community, I’m pleased to announce the release of Spring Security 5.3.0.M1! You can find the complete details in the release notes and the highlights below:

SAML

gh-7654 - Allow configuration of AuthenticationManager in saml2Login()
gh-7681 - Make Saml2Authentication serializable

OAuth 2.0

gh-5385 - Resource server support for multiple trusted JWT access token issuers
gh-7569 - Reactive implementation of AuthorizedClientServiceOAuth2AuthorizedClientManager
gh-7592 - Add OidcIdToken.Builder
gh-7593 - Add OidcUserInfo.Builder
Read more...

Spring for Apache Kafka 2.4 is Available

To support last week’s Apache Kafka 2.4.0 release, I am pleased to announce that the Spring for Apache Kafka 2.4 - 2.4.0.RELEASE - is available in maven central.

This version is essentially functionally equivalent to 2.3.x, but is compiled against the 2.4.0 kafka-clients and supports the new incremental rebalancing protocol.

The 2.4.0 kafka-clients are not binary compatible with Spring for Apache Kafka 2.3 so if you wish to use the 2.4.0 clients, you must upgrade to this version. See the appendix in the reference manual for how to override the jar versions, especially if you are using Spring Boot for dependency management and/or you are using the test embedded Kafka broker.

Read more...

Spring Cloud Roadmap and Hoxton and Greenwich Maintenance and EOL Announcements

With the recent Spring Framework and Spring Boot maintenance and roadmap posts, the Spring Cloud team is taking the opportunity to provide some insight to our future roadmap as well as the lifetimes of the Greenwich and Hoxton release trains.

Spring Cloud Ilford

We would like to announce our next major release, Spring Cloud Ilford. This will be the first major release since the release of Spring Cloud Finchley, which provided support for Spring Boot 2.x and Spring Framework 5.x. By making Ilford a major release, it will allow us to remove modules that have entered maintenance mode and to complete the simplification of the release train announced earlier this year. It will also allow us to do some API refactoring that may introduce breaking changes.

Read more...

Spring Cloud Hoxton Service Release 1 (SR1) is available.

On behalf of the community, I am pleased to announce that the Service Release 1 (SR1) 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

This milestone was primarily a bugfix release.

Please see the Hoxton.SR1 Github Project for all issues closed.

This milestone release is built with Spring Boot 2.2.2.RELEASE.

Spring Cloud Config

Besides bug fixes, Vault authentication was changed to use the Spring Vault project providing more options. Plain text resources are now available through the AWS S3 environment repository.

Read more...

Spring Tools 4.5.0 released

Dear Spring Community,

I am happy to announce the 4.5.0 release of the Spring Tools 4 for Eclipse, Visual Studio Code, and Theia.

Highlights from this release include:

  • (Eclipse): Spring Tools 4 for Eclipse distribution updated to Eclipse 2019-12 release
  • (Eclipse) improvement: progress updates from new live hover mechanism now appears in Eclipse as well
  • (Eclipse) bugfix: fixed NPE when deleting apps from CF via the boot dashboard
  • (Eclipse) bugfix: finish button was disabled after selecting an org/space when creating a CF target in the boot dashboard
  • (Spring Boot) improvement: better and more consistent labels for running processes in live hover actions across the board
  • various improvements to the Spring Tools 4 user guide
  • bugfixes
Read more...

Spring for Apache Kafka 2.4 Release Candidate

Hot on the heels of the recent Apache Kafka 2.4.0 release, I am pleased to announce the release candidate for Spring for Apache Kafka 2.4 - 2.4.0.RC1 - is available in the Spring milestone repository.

This version is essentially functionally equivalent to 2.3.x, but is compiled against the 2.4.0 kafka-clients and supports the new incremental rebalancing protocol.

The 2.4.0 kafka clients are not binary compatible with Spring for Apache Kafka 2.3 so if you wish to use the 2.4.0 clients, you must upgrade to this version. See the appendix in the reference manual for how to override the jar versions, especially if you are using Spring Boot and/or the test embedded kafka broker.

Read more...

Spring Boot for Apache Geode & Pivotal GemFire 1.1.4.RELEASE & 1.2.2.RELEASE Available

On behalf of the Spring, Apache Geode & Pivotal GemFire communities, it is my pleasure to announce the release of Spring Boot for Apache Geode & Pivotal GemFire (SBDG) 1.1.4.RELEASE as well as 1.2.2.RELEASE.

Both releases are available in Maven Central.

What’s New

While SBDG 1.1.4.RELEASE primarily aligns with the latest Spring bits in its release line:

  • Spring Framework 5.1.12.RELEASE

  • Spring Boot 2.1.11.RELEASE

  • Spring Data Lovelace-SR14/2.1.14.RELEASE

  • Spring Session for Apache Geode & Pivotal GemFire (SSDG) Bean-SR8/2.1.7.RELEASE (NEW)

And SBDG 1.2.2.RELEASE builds on:

  • Spring Framework 5.2.2.RELEASE

  • Spring Boot 2.2.2.RELEASE

  • Spring Data Moore-SR3/2.2.3.RELEASE

  • Spring Session for Apache Geode & Pivotal GemFire (SSDG) Corn-RELEASE/2.2.1.RELEASE (NEW)

  • Spring Test for Apache Geode & Pivotal GemFire (STDG) 0.0.11.RELEASE (NEW)

SBDG 1.2.2.RELEASE additionally includes the following improvements:

  • Enhancements to @EnableClusterAware Region bean detection.

  • Changes the Pool used in the Spring Session Starter from (the legacy SDG) "gemfirePool" to the Apache Geode "DEFAULT" Pool for convenience, especially when getting started.

See here for more details.

See the changelog for complete details.

Read more...

Spring Session for Apache Geode & Pivotal GemFire 2.1.7.RELEASE and 2.2.1.RELEASE Available

On behalf of the Spring, Apache Geode and Pivotal GemFire communities, it is my pleasure to announce the release of Spring Session for Apache Geode & Pivotal GemFire (SSDG) 2.1.7.RELEASE as well as 2.2.1.RELEASE.

Both releases are available in Maven Central.

What’s New

While SSDG 2.1.7.RELASE primarily aligns with the latest Spring bits in its respective line:

  • Spring Framework 5.1.12.RELEASE

  • Spring Boot 2.1.11.RELEASE

  • Spring Data Lovelace-SR14/2.1.14.RELEASE

  • Spring Session Bean-SR8/2.1.9.RELEASE

And SSDG 2.2.1.RELEASE aligns with:

  • Spring Framework 5.2.2.RELEASE

  • Spring Boot 2.2.2.RELEASE

  • Spring Data Moore-SR3/2.2.3.RELEASE

  • Spring Session Corn-RELEASE/2.2.0.RELEASE

SSDG 2.2.1.RELEASE additionally includes the following improvements:

  • Converts all Spring Session OQL Indexes from HASH to FUNCTIONAL (RANGE) Indexes.

  • Adds support to disable OQL Indexes created by SSDG.

  • And enhances the PdxSerializableSessionSerializer to mark the PDX identity field using the Session ID.

See here for full details.

Read more...

Spring Boot 2.1.x EOL November 1st 2020

With the recent release of Spring Boot 2.2, we’d like to announce that maintenance for Spring Boot 2.1 will end on November 1st 2020.

We’ll keep publishing the occasional maintenance release up until that point, but we recommend that all users consider upgrading to Spring Boot 2.2 as soon as possible. Upgrading to Spring Boot 2.2 from 2.1 should not be too difficult, and upgrade instructions are available on the WIKI.

In order to help track the state of supported releases we’ve also introduced a new “supported versions” WIKI page. You can see at a glance which Spring Boot versions are supported and when they will EOL.

Read more...

Spring Cloud Data Flow 2.3.0 GA Released

The release 2.3.0 delivers a lot of enhancements and generic compatibility changes for Spring Boot 2.2.x and Spring Cloud Hoxton.

Continuous Deployment For Tasks

As task applications evolve faster to keep up with business needs, the ability for new versions to be consumed via Data Flow in an automated way is needed. While Data Flow has supported the ability to register multiple versions of a task application in previous iterations, the ability to run them in a practical way by re-hydrating command line arguments, deployment properties, and application properties used in previous executions has been missing. In this version, the storage of those values in a manifest and the ability to both retrieve them to determine if an application needs to be upgraded and apply them to the new execution allows for developers to create continuous deployment flows for their task applications. All these capabilities are readily available through RESTful APIs, as well, so the overall CI/CD workflow for Tasks can be automated.

Read more...