Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreWe're excited to announce Spring AI 1.0.0 RC1, marking the final set of breaking changes, bug fixes, and new functionality before the stable release! The GA version is scheduled for May 20th, 2025 - just one week away. During this time, we'll be focusing on improving documentation and addressing any reported bugs.
To celebrate this release, we have added a new song to our AI-generated music playlist Check out the latest track to enhance your blog reading and coding experience.
In VectorStoreChatMemoryAdvisor
:
CHAT_MEMORY_RETRIEVE_SIZE_KEY
→ TOP_K
DEFAULT_CHAT_MEMORY_RESPONSE_SIZE
(100) → DEFAULT_TOP_K
(20)CHAT_MEMORY_CONVERSATION_ID_KEY
→ CONVERSATION_ID
(moved to ChatMemory
interface)
org.springframework.ai.chat.memory.ChatMemory.CONVERSATION_ID
Advisors now use independent templates with specific required placeholders:
QuestionAnswerAdvisor
: query
, question_answer_context
PromptChatMemoryAdvisor
: instructions
, memory
VectorStoreChatMemoryAdvisor
: instructions
, long_term_memory
In 1.0.0-RC1, we've standardized the naming pattern for chat memory components by adding the repository
suffix throughout the codebase. This change affects Cassandra, JDBC, and Neo4j implementations:
All memory-related artifacts now follow a consistent pattern:
spring-ai-model-chat-memory-*
→ spring-ai-model-chat-memory-repository-*
spring-ai-autoconfigure-model-chat-memory-*
→ spring-ai-autoconfigure-model-chat-memory-repository-*
spring-ai-starter-model-chat-memory-*
→ spring-ai-starter-model-chat-memory-repository-*
.repository.
segmentorg.springframework.ai.chat.memory.jdbc
→ org.springframework.ai.chat.memory.repository.jdbc
Repository
suffixJdbcChatMemoryAutoConfiguration
→ JdbcChatMemoryRepositoryAutoConfiguration
spring.ai.chat.memory.<storage>...
to spring.ai.chat.memory.repository.<storage>...
include-prompt
→ log-prompt
)All deprecations have been removed for a cleaner API. For complete details, see the Spring AI Upgrade Notes.
Added dedicated DeepSeek model support with core classes and starter, accommodating its divergence from the OpenAI API.
There were other refactoring, bug fixing, documentation enhancements across the board by a wide range of contributors. If we haven't gotten to your PR yet, we will, please be patient. Thanks to