Should springboot provide a plug-in to solve the problem that the dependent software versions are not matched in the large version upgrade of springboot？

Spring Boot itself depends on many other software, and the version requirements for some dependent software will change each version upgrade, especially the release of large versions. For users, unless all dependent software uses the default version provided by springboot, upgrading springboot will cause the problem that the dependent software version is not matched. Especially for the upgrade between large versions, this problem is particularly serious. As far as I know, every time the official releases a new version, it will specifically explain the changes of the dependent software version. However, this description is only for the changes of the previous version. There is no place to find the description of changes across versions, especially between large versions.

If there is a plug-in or a starter that tells users which software versions in the project do not meet the requirements of the current spring boot version, upgrading the version is no longer a terrible thing for users.

No files, tests, or entry points are identified in the issue. Start by reviewing Spring Boot's dependency-version management and upgrade behavior, then define how a plug-in or starter would detect incompatible dependent software versions across major upgrades; done would mean a concrete, testable proposal for reporting those mismatches.