Madhura Bhave

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

This release contains almost 70 closed issues and pull requests which include bug fixes, documentation updates and dependency upgrades. Thanks to everyone who contributed with issue reports and pull requests.

How can you help?

If you’re interested in helping out, check out the “ideal for contribution” tag in the issue repository. If you have general questions, please ask on stackoverflow.com using the spring-boot tag or chat with the community on Gitter.

On behalf of the team and everyone that contributed, I am happy to announce that the fourth milestone of Spring Boot 2.1 has been released and is available from our milestone repository. This release closes over 40 issues and pull requests.

This milestone ships with the latest Spring Framework 5.1 which went GA last week.

Along with the Spring Framework update, this release also includes a bunch of other dependency version updates.

For a complete list of changes and upgrade instructions, please see the Spring Boot 2.1 Release Notes on the wiki and the updated reference documentation.

Auto-configuration is one of the most powerful features of Spring Boot. Tests for auto-configuration classes usually follow the same pattern. Most tests start up an ApplicationContext with the auto-configuration class under test and depending on the test, also load additional configuration to simulate user behavior. The recurrence of this pattern can add a lot of repetition in the code base.

Spring Boot 2.0 provides a suite of new test helpers for easily configuring an ApplicationContext to simulate auto-configuration test scenarios. The following example configures an ApplicationContextRunner to test the UserServiceAutoConfiguration:

Milestone 4 of Spring Boot 2.0 brings important changes to the security auto-configuration provided by Spring Boot.

Problem Statement

Until Spring Boot 1.x, the default auto-configuration secured all of the application endpoints using basic authentication. If actuator was on the classpath, there was a separate security configuration that applied to the actuator endpoints. The way these two auto-configurations would turn on and off was completely independent. Because of this, users wanting to provide custom security found themselves fighting ordering issues with WebSecurityConfigurerAdapters.

The third milestone of Spring Boot 2.0 is available now from the Spring milestone repository. This milestone ensures compatibility with Spring Framework 5.0.0.RC3 and contains a number of other dependency upgrades. This release closes over 100 issues and pull requests, thanks to all that contributed!

For a complete list of changes, and upgrade instructions, see the Spring Boot 2.0.0.M3 Release Notes on the WIKI and the updated reference documentation.

If you want to get started and discover the new features, you can easily bootstrap a new project on https://start.spring.io

Spring Boot v1.5.0.RC1 is available now from the Spring milestone repository. This release closes over 220 issues and pull requests! Thanks to everyone that has contributed!

Highlights of the new release include:

• Out of the box security for actuators
• Auto-configured @IntegrationComponentScan
• Auto-detection of spring.jpa.database
• Support for Apache Kafka
• Support for Cloud Foundry and actuator integration
• Support for embedded in-memory LDAP server and auto-configuration for any compliant LDAP server
• Upgrades to Spring Data Ingalls, Jetty 9.4, JooQ 3.9, AssertJ 2.6.0, Hikari 2.5 and Neo4J 2.1 and more
• Upgrades to several Maven plugins