Tracks the Spring Boot 3.x → 4.x migration in `cycles-server-admin`. Currently blocks #152 and is the peer of `runcycles/cycles-server#134`.
Why this isn't a Dependabot merge
Springdoc 3.x is built against Spring Boot 4 and pulls in SB4 autoconfigs that conflict with this repo's SB3 baseline:
```
BeanDefinitionOverrideException: Invalid bean definition with name 'conventionErrorViewResolver'
- defined in: org.springframework.boot.webmvc.autoconfigure.error.ErrorMvcAutoConfiguration (SB4 path)
- already bound: org.springframework.boot.autoconfigure.web.servlet.error.ErrorMvcAutoConfiguration (SB3 path)
```
SB4 moved `ErrorMvcAutoConfiguration` from `autoconfigure.web.servlet` → `webmvc.autoconfigure`. Both class paths exist on the classpath simultaneously when SB4 transitives meet an SB3 base, hence the override exception. Springdoc 3 cannot merge until SB4 lands.
Scope of the migration
Cross-repo
Recommend doing all three in coordinated PRs so we don't have an SB3 ↔ SB4 mixed-version run in production.
Reference
Tracks the Spring Boot 3.x → 4.x migration in `cycles-server-admin`. Currently blocks #152 and is the peer of `runcycles/cycles-server#134`.
Why this isn't a Dependabot merge
Springdoc 3.x is built against Spring Boot 4 and pulls in SB4 autoconfigs that conflict with this repo's SB3 baseline:
```
BeanDefinitionOverrideException: Invalid bean definition with name 'conventionErrorViewResolver'
```
SB4 moved `ErrorMvcAutoConfiguration` from `autoconfigure.web.servlet` → `webmvc.autoconfigure`. Both class paths exist on the classpath simultaneously when SB4 transitives meet an SB3 base, hence the override exception. Springdoc 3 cannot merge until SB4 lands.
Scope of the migration
Cross-repo
Recommend doing all three in coordinated PRs so we don't have an SB3 ↔ SB4 mixed-version run in production.
Reference