The Spring Blog

News and Events

Spring Tools 4.4.2 released

Dear Spring Community,

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

Highlights from this release include:

  • (Spring Boot), (Eclipse) enhancement: new actions to connect/refresh/disconnect live hover information for running Spring Boot projects now available from the Boot Dashboard menus (context-menu + view toolbar)
  • (Spring Boot), (Eclipse) enhancement: Optional link console tab with Boot Dashboard selection (#386)
  • (Spring Boot), (VSCode): early version of more detailed progress reporting for live hover information mechanism
  • (Concourse) enhancement: various updates
  • bugfixes

Spring Cloud Greenwich.SR4 Released

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

Notable Changes in the Greenwich Release Train

Spring Cloud Greenwich.SR4 is built upon Spring Boot 2.1.10.RELEASE.

Spring Cloud Kubernetes

Spring Cloud Commons

Spring Cloud Openfeign

Spring Cloud Contract


Spring Data Moore SR2 and Lovelace SR13 available

On behalf of the community, I’m pleased to announce the availability of the Spring Data Moore SR2 and Lovelace SR13 service releases.

Both releases fix 66 tickets in total, mostly bugfixes. We decided to ship both versions on short notice to address bugs around auditing and converter registration for a broader range of users, as we’ve noted an increased number of bug reports in both areas. If you use Spring Data through Spring Boot, you can consume the released artifacts by setting the spring-data-releasetrain.version property to Moore-SR2 or Lovelace-SR13.


Spring Cloud Open Service Broker 3.1.0.RC1 Released

We are pleased to announce the 3.1.0.RC1 release of Spring Cloud Open Service Broker. Support for Open Service Broker API v2.15 is now feature complete, and we expect for this to be the final milestone before a GA release. Thanks to the community for your feedback and contributions! This release includes the following fixes and enhancements:

  • Upgrade to Spring Boot 2.2.1.RELEASE
  • Add ServiceBrokerMaintenanceInfoConflictException to handle MaintenanceInfoConflict error scenarios.
  • ServiceBrokerInvalidParametersException now returns an HTTP 400 when a create or update request is malformed or includes invalid parameters. Previously it was, incorrectly, returning an HTTP 422.
  • CreateServiceInstanceBindingRequest now extends AsyncParameterizedServiceInstanceRequest in order to utilize a common request object and reduce redundancy.
  • Update reference documentation.

Spring Cloud Hoxton.RC2 Released

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

Notable Changes in the Hoxton Release Train

Spring Cloud Hoxton.RC2 is built upon Spring Bot 2.2.1.RELEASE.

Spring Cloud Vault

Spring Cloud Circuitbreaker

Spring Cloud Gateway


Spring Boot for Apache Geode & Pivotal GemFire 1.1.3.RELEASE & 1.2.1.RELEASE Available

On behalf of the Spring, Apache Geode, Pivotal GemFire and Pivotal Cloud Cache communities, it is my pleasure to announce the release of Spring Boot for Apache Geode & Pivotal GemFire (SBDG) 1.1.3.RELEASE and 1.2.1.RELEASE.

SBDG 1.1.3.RELEASE builds on the new Spring Boot 2.1.10.RELEASE.

SBDG 1.2.1.RELEASE builds on the new Spring Boot 2.2.1.RELEASE.

Both versions are available in Maven Central.

See the changelog for full details of the changes in these releases.


As always, feedback is most welcomed and appreciated. Give the new bits a try and let us know what you think.


Spring Vault 2.2 goes GA

On behalf of the community, I’m excited to announce that Spring Vault 2.2 is generally available from as well as Maven Central. This release ships with several refinements and new features.

The most notable changes are:

  • Support for PCF-based authentication by using instance identity certificates.

  • Extensions for a seamless Kotlin 1.3 experience and Kotlin Coroutines support.

  • Builders for RestTemplate and WebClient to customize interceptors, filter functions, and default headers.

  • Vault namespace support (Vault Enterprise edition only).

  • A revised @VaultPropertySource supporting versioned key-value backends.

  • Added listener and events support to LifecycleAwareSessionManager.

  • Support for the Jetty HTTP Client as an alternative reactive HTTP client.

  • Reactive support for AWS IAM authentication.


Spring Boot 2.2.1 available now

On behalf of the team and everyone who has contributed, I’m happy to announce that Spring Boot 2.2.1 has been released and is now available from and Maven Central.

This release includes 110 fixes, improvements, and dependency upgrades. Thanks to all those who have contributed with issue reports and pull requests.

For those of you upgrading from Spring Boot 2.2.0 to Spring Boot 2.2.1, if you relied on the @ConfigurationProperties scanning support, please note that this feature is now disabled by default. Scanning of @ConfigurationProperties needs to be explicitly opted into by adding the @ConfigurationPropertiesScan annotation. More details related to this change can be found here.


Spring Integration Extensions Releases

Dear Spring Community,

Following several requests from community members, it is my pleasure to announce that some Spring Integration Extensions have made it to their new generations and up-to-date dependencies. Of course, first of all, thank you everybody contributed, even if that was just a GitHub issue or StackOverflow question!

Below are highlights for those projects. All of them are available on Maven Central, JCenter and Spring Release repositories. Since all these projects are not a part of Spring Integration BOM (and they cannot be because of different release cycles) you have to specify their versions in your dependency management explicitly.