RepoJournal
Spring @spring-projects
107 wires and counting
$ status: archived — this briefing has stopped; the archive stays readable. browse live briefings →

$ status

wire 2026-06-28
stories 35
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

SPRING FRAMEWORK AND BOOT PURGE DEPRECATION WARNINGS AHEAD OF GRADLE 10

By RepoJournal · Filed · About Spring · Composed from the cited sources · methodology

dlwldnjs1009
1 person shipped this
dlwldnjs1009 @dlwldnjs1009 2 cited

Spring Framework is systematically eliminating deprecation warnings across the codebase as Gradle 9.6 forces the migration to modern APIs.

The framework team addressed internal and public deprecations spanning deprecated Locale constructors, URL constructors, and Thread#getId calls [1]. This cleanup is tied to a Gradle upgrade that's already emitting warnings of its own. The Gradle 9.6.0/9.6.1 jump deprecated Project.getProperties() and will remove it entirely in Gradle 10.0, forcing Spring Framework to migrate TestConventions and build scripts to use findProperty() instead [2]. Over in Boot land, the team is squashing a trio of bugs where Actuator fails to refresh on Jersey and Cloud Foundry when spring-boot-health is absent [3] [4]. The fix moves health-specific beans into nested configurations so management endpoints can load without the health module present [5]. Meanwhile, OpenTelemetry documentation got clarified on service.name and service.namespace defaults [6].

Action items

References

  1. [1] Address deprecation warnings ↗ spring-projects/spring-framework
  2. [2] Avoid Gradle deprecation warnings ↗ spring-projects/spring-framework
  3. [3] Context refresh fails when using Actuator on Jersey without spring-boot-health ↗ spring-projects/spring-boot
  4. [4] Context refresh fails on Cloud Foundry when using Actuator without spring-boot-health ↗ spring-projects/spring-boot
  5. [5] Avoid loading health classes in Jersey config ↗ spring-projects/spring-boot
  6. [6] Update OpenTelemetryResourceAttributes documentation ↗ spring-projects/spring-boot

$ ls spring-projects/reviews/ # the step-back reads

the week in review Spring Kafka fixes multi-value JSON header loss the month in review Spring standardizes release trains while security patches and batch fixes surface
Full archive → Weekly reviews →

Quick answers

What shipped in Spring on June 28, 2026?
Spring Framework is systematically eliminating deprecation warnings across the codebase as Gradle 9.6 forces the migration to modern APIs. In total, 29 commits and 6 pull requests landed.
Who contributed to Spring on June 28, 2026?
1 developer shipped this update, including dlwldnjs1009.
What were the notable Spring updates?
Address deprecation warnings, Avoid Gradle deprecation warnings, and Context refresh fails when using Actuator on Jersey without spring-boot-health.
♥

$ log @spring-projects --recent

Kubernetes probe groups keep their defaults; multi-segment health paths land 90 shipped Kafka config building centralized, async listener results awaited on stop 52 shipped Spring Data moves to JSqlParser 5.4 and Hibernate 7.4.8.Final 11 shipped Spring Batch deprecates setters for required dependencies 5 shipped

$ log --all # elsewhere on the wire

Agent Security Quiet day in agent security as guard coverage reaches four clients Alignment & Post-training verl defaults Ascend RL mode, open-instruct unblocks SFT packing

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.