RepoJournal
Spring

@spring-projects

Spring Framework, Spring Boot, and the JVM enterprise layer

Pick a date

  1. Thu 21 may
  2. Sat 23 may
  3. Sun 24 may
  4. Mon 25 may
  5. Tue 26 may
  6. Wed 27 may
  7. Thu 28 may
  8. Fri 29 may
  9. Sat 30 may
  10. Sun 31 may
  11. Mon 1 jun
  12. Mon 8 jun
  13. Tue 9 jun
  14. Wed 10 jun
  15. Thu 11 jun
  16. Fri 12 jun
  17. Sat 13 jun
  18. Sun 14 jun
  19. Mon 15 jun
  20. Tue 16 jun
  21. Wed 17 jun
  22. Thu 18 jun
  23. Sat 27 jun
  24. Sun 28 jun
  25. Mon 29 jun
  26. Tue 30 jun
  27. Wed 1 jul
  28. Thu 2 jul
  29. Fri 3 jul
  30. Today 4 jul

The Wire · Showcase

Spring AI fixes MCP API deprecation, protobuf versioning conflicts

By RepoJournal · Filed · About Spring

Spring AI removed deprecated MCP API calls and resolved a critical protobuf version mismatch with Spring Boot 4.x that was shadowing newer versions across vector stores.

The Spring AI team cleaned up deprecated MCP API calls [1], closing out technical debt before the next major release. In parallel, they removed explicit protobuf-java version pins from the root pom.xml [2], trusting Spring Boot 4.x's bom import at 4.35.0 instead of the older 3.25.8 and 4.29.3 pins that were causing conflicts in downstream modules. This matters because the pinned versions were overriding Spring Boot's dependency management in spring-ai-qdrant-store and spring-ai-milvus-store, potentially leaving those stores vulnerable or incompatible. Spring AI also fixed OpenSearchVectorStore deserialization [4] by handling a Jackson 2 vs Jackson 3 mismatch where the OpenSearch client couldn't deserialize into Jackson 3 annotated POJOs. On the tooling side, Google GenAI ToolChoice now properly handles VALIDATED mode [5] and defaults to AUTO when only allowed-function-names is set, preventing opaque startup failures. Spring Data Elasticsearch upgraded to 9.4.3 [3], and Spring AMQP bumped JUnit to 6.1.1 [6] and HttpClient5 to 5.6.2 [7] for dev dependencies.

Action items

References

  1. [1] Remove calls to deprecated MCP API spring-projects/spring-ai
  2. [2] Remove explicit `protobuf-java` version properties spring-projects/spring-ai
  3. [3] Upgrade Elasticsearch to 9.4.3 ↗ spring-projects/spring-data-elasticsearch
  4. [4] Fix `OpenSearchVectorStore` document deserialization ↗ spring-projects/spring-ai
  5. [5] Fix Google GenAI ToolChoice VALIDATED mode and defaults spring-projects/spring-ai
  6. [6] Bump org.junit:junit-bom from 6.1.0 to 6.1.1 ↗ spring-projects/spring-amqp
  7. [7] Bump org.apache.httpcomponents.client5:httpclient5 from 5.6.1 to 5.6.2 in the development-dependencies group ↗ spring-projects/spring-amqp

FAQ

What changed in Spring on July 4, 2026?
Spring AI removed deprecated MCP API calls and resolved a critical protobuf version mismatch with Spring Boot 4.x that was shadowing newer versions across vector stores.
What should Spring teams do about it?
Review and test protobuf imports in custom vector stores if you extend spring-ai-qdrant-store or spring-ai-milvus-store • Test OpenSearchVectorStore deserialization if using OpenSearch with Spring AI • Verify Google GenAI tool-choice configuration if relying on allowed-function-names defaults
Which Spring repositories shipped on July 4, 2026?
spring-projects/spring-ai, spring-projects/spring-data-elasticsearch, spring-projects/spring-amqp

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.