The Wire · Showcase
SPRING AI 2.0.0-M8 SHIPS WITH BREAKING PROPERTY CHANGES
By RepoJournal · Filed · About Spring
Spring AI's milestone release forces a migration to dash-separated configuration properties, while Spring Framework patches class scanning conflicts and WebSocket handling bugs.
Spring AI 2.0.0-M8 landed overnight with a significant shift to Spring Boot naming conventions [1]. The breaking change to dash-separated properties will require config updates across deployments, but the release also cleans up dependency bloat in the Google GenAI starter [2] and ships improved MistralAi support with reasoning model parameters [3]. Meanwhile, Spring Framework addressed a scanned class removal bug that could silently drop beans when imports conflict [4], a critical fix for teams relying on classpath scanning. The security team reverted snapshot dependency testing across multiple commits [ref:2, 3, 4] after discovering issues, though the original snapshot test infrastructure [ref:5, 6] remains intact for future refinement. Spring Session bumped Logback to 1.5.33 [10] for tag escaping improvements, a routine but necessary maintenance update. Smaller Framework wins include a JettyWebSocketSession last-flag fix [11] and pinned Node.js to 24.15.0 to unblock documentation builds [12].
Action items
- → Plan migration to dash-separated properties in Spring AI configs before next AI module upgrade spring-projects/spring-ai [plan]
- → Upgrade Spring Framework to get the class scanning conflict fix if you use component scanning with imports spring-projects/spring-framework [plan]
- → Update Logback to 1.5.33 in Spring Session deployments on next maintenance cycle spring-projects/spring-session [monitor]
References
- [1] Spring AI 2.0.0-M8 ↗ spring-projects/spring-ai
- [2] Refine spring-ai-starter-model-google-genai dependencies spring-projects/spring-ai
- [3] Improve MistralAiApi Jackson mapping for message content spring-projects/spring-ai
- [4] Remove scanned class only when conflicting with imported class spring-projects/spring-framework
- [5] Partial revert fe2e52f646f6beb534de2e49152c183c6e5a1529 spring-projects/spring-security
- [6] Revert "Add Test Against Snapshot" spring-projects/spring-security
- [7] Revert "Add Test Against Snapshots" spring-projects/spring-security
- [8] Add Test Against Snapshots spring-projects/spring-security
- [9] Add Test Against Snapshots spring-projects/spring-security
- [10] Bump ch.qos.logback:logback-core from 1.5.32 to 1.5.33 ↗ spring-projects/spring-session
- [11] Fix last flag check in JettyWebSocketSession spring-projects/spring-framework
- [12] Pin Node.js version to 24.15.0 spring-projects/spring-framework
FAQ
- What changed in Spring on May 28, 2026?
- Spring AI's milestone release forces a migration to dash-separated configuration properties, while Spring Framework patches class scanning conflicts and WebSocket handling bugs.
- What should Spring teams do about it?
- Plan migration to dash-separated properties in Spring AI configs before next AI module upgrade • Upgrade Spring Framework to get the class scanning conflict fix if you use component scanning with imports • Update Logback to 1.5.33 in Spring Session deployments on next maintenance cycle
- Which Spring repositories shipped on May 28, 2026?
- spring-projects/spring-ai, spring-projects/spring-framework, spring-projects/spring-security, spring-projects/spring-session