97 wires and counting

$ follow Spring

Keep up with Spring in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-08-30
stories 11

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Spring improves singleton destruction caching, upgrades Elasticsearch and Boot deps

By RepoJournal · Filed · About Spring

Spring Framework improves singleton destruction handling while Spring Data Elasticsearch moves to 9.5.2 and Spring Kafka bumps Boot to 4.0.8.

Spring Framework switched to the singleton target as the cache key for destruction purposes [1], closing gh-37207. This means destruction caching now keys on the actual target bean, preventing mismatches when proxies or aliases are involved. Separately, a lock-guarded boolean field was reduced to a thread-local [2], closing gh-37199 and eliminating lock contention on that hot path. Spring Data Elasticsearch upgraded to Elasticsearch 9.5.2 [3], closing #3333, bringing the client in line with the latest server release. In the same vein, Spring Batch Extensions bumped spring-boot-starter-parent from 4.0.3 to 4.1.1 [4], and Spring Kafka updated its development dependencies, moving spring-boot-starter from 4.0.7 to 4.0.8 [5]. The Kafka build also tracks Spring Data's BOM from 2026.1.0-M1 to 2026.1.0-SNAPSHOT [6], keeping alignment with upcoming milestones. Finally, a flaky Spring Integration test was fixed [7]: the mocked MessageSource now properly terminates its polling sequence, so the test no longer fails on loaded CI runners.

Action items

References

  1. [1] Use singleton target as cache key for destruction purposes ↗ spring-projects/spring-framework
  2. [2] Reduce lock-guarded boolean field to thread-local ↗ spring-projects/spring-framework
  3. [3] Upgrade to Elasticsearch 9.5.2. ↗ spring-projects/spring-data-elasticsearch
  4. [4] Bump `spring-boot-starter-parent` from 4.0.3 to 4.1.1 ↗ spring-projects/spring-batch-extensions
  5. [5] Bump org.springframework.boot:spring-boot-starter from 4.0.7 to 4.0.8 in the development-dependencies group ↗ spring-projects/spring-kafka
  6. [6] Bump org.springframework.data:spring-data-bom from 2026.1.0-M1 to 2026.1.0-SNAPSHOT ↗ spring-projects/spring-kafka
  7. [7] Fix flaky MockMessageSourceTests.testMockMessageSource() ↗ spring-projects/spring-integration

Quick answers

What shipped in Spring on August 30, 2026?
Spring Framework improves singleton destruction handling while Spring Data Elasticsearch moves to 9.5.2 and Spring Kafka bumps Boot to 4.0.8. In total, 8 commits and 3 pull requests landed.
Who contributed to Spring on August 30, 2026?
5 developers shipped this update, including Artem Bilan, Juergen Hoeller, Stefano Cordio, sothawo, and dependabot.
What were the notable Spring updates?
Use singleton target as cache key for destruction purposes, Reduce lock-guarded boolean field to thread-local, and Upgrade to Elasticsearch 9.5.2.