Previously, the list of modules for a particular version of Boot was
hard-coded. When this list got of a sync with a version's actual
modules, the changelog would become inaccurate as the generator would
not have a complete view of all of the version's metadata.
This commit addresses this by resolving the list of modules for a
particular version from its dependency management declared in
spring-boot-dependencies.
Closes gh-49336
This commit fixes the changelog generator to not flag two identical
arrays as changed. Previously, any candidate property with an array
of default values were flagged incorrectly.
Closes gh-49272
This commit adds a new section in the Configuration Changelog to
indicate properties whose default values have changed.
See gh-48962
Signed-off-by: junpak <junpak.park@gmail.com>
Rather than listing common modules and tweak things for various
milestones, this commit flatten the list of modules as of Spring Boot
4.0.0-RC1.
Closes gh-47852
This commit handles a corner case where we have to add properties in
a release that represents something we mean to remove but that's not
ready to go away just yet.
Those properties are now considered in the changelog, but marked as
deprecated.
Closes gh-47759
Introduce NullMarkedExtension for ArchitectureCheck, which provides
functionality to configure packages to ignore in nullability checks and
to enable or disable the extension.
See gh-47596
Signed-off-by: Dmytro Nosan <dimanosan@gmail.com>
This commit shades the use of 'com.vaadin.external.google:android-json'
in the three modules that use it. The configuration processor already
did that and this commit does the same for configuration-metadata and
the CLI.
As a result of this commit, 'android-json' is not used nor managed
internally.
Closes gh-45504
This commit removes OptionalParameter in favor of the nullness support
introduced in Spring Framework 7. The parameter of an action can now
be flagged as optional using JSpecify's @Nullable, and simplifies the
setup for those who are using JSpecify as only a single annotation is
required.
Closes gh-45390
Remove `@Nullable` support for optional endpoint method parameters in
favor of only supporting `@OptionalParameter`. The annotation processor
now also only supports `@OptionalParameter` detection.
Closes gh-47136
Spring Boot 4 requires Jakarta EE 11. Jersey 4 will support EE 11 but
its release schedule is uncertain. Furthermore, Jersey does not yet
support Jackson 3 and there's no clear timeline for when Jackson 3
will be supported.
In light of the above, this commit removes support for Jersey.
Reinstating support can be considered once there's a Jersey GA that
supports Jakarta EE 11 or its clear that one will be available in
time for Boot's GA in November. Ideally, support for Jackson 3 would
also be available before reinstating Jersey support.
Closes gh-47017
Spring Framework 7.0 requires a Servlet 6.1 baseline for Servlet containers.
Partial Servlet 6.1 support is available on the `main` Undertow branch,
but there isn't any milestone version available for the undertow 2.4
generation. At this stage of our 4.0 schedule, we think it's safer to drop
Undertow support now.
Closes: gh-46917
This commit expands the detection of optional parameters for Actuator
Endpoints. Before this commit, JSpecify's `@Nullable` annotation was
not detected.
See gh-46854
Signed-off-by: wonyongg <111210881+wonyongg@users.noreply.github.com>
Projects which don't have JSpecify nullability annotations can opt out
by using
architectureCheck {
nullMarked = false
}
in their build.gradle script.
See gh-46587
Andy Wilkinson
Stéphane Nicoll
Phillip Webb
junpak
Moritz Halbritter
Dmytro Nosan
Brian Clozel
wonyongg