When running Spring Application Advisor commands such as:
advisor upgrade-plan get
However, the command ends with:
No explicit blocking dependency or error is reported
But consulting the official Spring Cloud ↔ Spring Boot compatibility matrix published by the Spring project, it shows that:
Spring Cloud 2025.1 (Oakwood) supports Spring Boot 4.0.x
In this release train, spring-cloud-function is version 5.0.x
This confirms that:
spring-cloud-function 5.0.x is compatible with Spring Boot 4.0.x
Therefore, an upgrade path from spring-cloud-function 4.3.x to 5.0.x should exist, even though it was not shown by Spring Application Advisor in the example above.
Spring Application Advisor 1.5.x
Spring Application Advisor relies on an internal upgrade mapping catalog to generate a safe and aligned upgrade plan across the Spring ecosystem.
This issue occurs when one or more required upgrade mappings are missing, incomplete, or incorrect, for example, a Spring ecosystem component (such as spring-cloud-function) does not yet have a defined upgrade mapping for the target Spring Boot version.
When Advisor cannot guarantee dependency alignment, it intentionally refuses to generate an upgrade plan, even though upgrade paths may be discovered.
This behavior is by design to prevent unsupported or unsafe dependency combinations.
To resolve the issue:
Open a support ticket with Broadcom Support.
Provide:
The Spring Application Advisor version
The build-config.json
The Advisor command output showing “No upgrade plans available”
Broadcom Support will:
Validate the missing or incorrect mappings
Provide an official workaround if available
Deliver an updated mapping via a patch release when applicable
Spring Application Advisor provides an advanced option to apply upgrades even when dependency alignment cannot be guaranteed:advisor upgrade-plan apply --accept-no-alignment
This option bypasses alignment safety checks and can be useful for evaluation or troubleshooting purposes. It should be used with caution and is not a replacement for resolving missing or incorrect upgrade mappings through Broadcom Support.