Is your feature request related to a problem? Please describe.
In applications using Spring Boot 4/Spring Framework 7, other libraries in the Spring portfolio switched to using the built-in retry features that superseded the old Spring Retry project (Batch, Integration, AMQP, Kafka, Pulsar...). When using Spring Cloud Config Client, it's necessary to add the extra Spring Retry dependency (which is maintenance only).
Describe the solution you'd like
It would be great if Spring Cloud Config could migrate from the deprecated Spring Retry library to Spring Framework's built-in RetryTemplate infrastructure.
Additional context
https://spring.io/blog/2025/09/09/core-spring-resilience-features
Is your feature request related to a problem? Please describe.
In applications using Spring Boot 4/Spring Framework 7, other libraries in the Spring portfolio switched to using the built-in retry features that superseded the old Spring Retry project (Batch, Integration, AMQP, Kafka, Pulsar...). When using Spring Cloud Config Client, it's necessary to add the extra Spring Retry dependency (which is maintenance only).
Describe the solution you'd like
It would be great if Spring Cloud Config could migrate from the deprecated Spring Retry library to Spring Framework's built-in
RetryTemplateinfrastructure.Additional context
https://spring.io/blog/2025/09/09/core-spring-resilience-features