Madhura Bhave

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 repo.spring.io 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.

On behalf of the team and everyone that contributed, I am pleased to announce that the release candidate for Spring Boot 2.2.0 is available from our milestone repository. This release contains 130 issues and pull requests.

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

We plan to make Spring Boot 2.2 generally-available in mid-October. Now is a great time to try out Spring Boot 2.2 and provide feedback so that we can try and fix things before GA. If you want to get started with 2.2 and try out the new features, you can bootstrap a new project on https://start.spring.io.

As mentioned in the announcement last year, the Spring Boot 1.x line has reached end of life. Spring Boot 1.5.22 which was released earlier today will be the last release in the 1.x. line.

We expect most users to have upgraded their applications to Spring Boot 2.x. For those that haven’t migrated yet, we strongly advise doing so as soon as possible. There are detailed instructions on how to migrate from 1.x to 2.x in the migration guide. For a smooth upgrade experience, we recommend upgrading in phases instead of jumping straight to the latest stable release. Once the upgrade from the latest 1.5.x version to the latest 2.0.x version is complete, you should upgrade to the latest release in the 2.1.x line.

On behalf of the team and everyone who has contributed, I am pleased to announce that Spring Boot 2.0.9 has been released and is now available from repo.spring.io and Maven Central.

This is a maintenance release that includes almost 40 dependency updates and selected bug fixes.

This is the last release in 2.0 line. Please consider upgrading to Spring Boot 2.1 if you haven’t already done so.

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.

The quickest way to generate Spring Boot projects is through start.spring.io. The site provides a curated list of dependencies that you can add to your application based on the selected Spring Boot version. You can also choose the language, build system and JVM version for the project. Over the years, the popularity of start.spring.io as the tool for generating Spring projects has grown exponentially and millions of projects are generated every year using the site.

For the past few months, we’ve been working on a complete overhaul of the project generation API. To better understand the motivation behind this, take a look at the project structure below:

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

This release includes 35 fixes, improvements and dependency upgrades. Thanks to all those who have 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’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.