📢 AssertJ joined the GitHub Secure Open Source Fund, a program that leveled up security across 67 open source projects.
What changed for us: SHA pinning, immutable releases, incident response plan, and a mindset shift toward security awareness 🔒
The impact? More robust JVM assertions 🚀
@GeePawHill glad to hear it! We'll do our best to improve Kotlin compatibility in version 4, stay tuned 🙂
📢 AssertJ 3.27.7 has been released!
This fixes CVE-2026-24400 🔒
Happy assertions!
https://github.com/assertj/assertj/releases/tag/assertj-build-3.27.7
Last but not least, the test suite is now much stronger as the relevant JSON marshalling is black-box tested.
If you're curious about the details, take a look at this PR 👇
https://github.com/spring-projects/spring-batch-extensions/pull/196
Jackson doesn't really need any introduction, and I lost track of how many times I wondered, "Can I really do this with Jackson?!"
After the changes, how the extension communicates with Notion is fully an implementation detail, tailored to its scope and no longer exposed to users. All public types are now decorated with Jackson annotations, and there is no need for an intermediate layer to handle request & response conversion.
Notion recently deprecated the database endpoints that Spring Batch Notion indirectly uses, and a new pattern should be adopted. Unfortunately, the maintainer has no bandwidth for this, so I've taken the opportunity to rewrite what is needed with the Spring HTTP Service Client and Jackson 3.
The HTTP Service Client really stands out for its brevity and ease of use. Plus, the versioning support introduced in Framework 7 is a perfect match for the Notion API.
🍃 Who replaced a third-party dependency with a Spring HTTP Service Client and is happy about it? 🙋♂️
In Spring Batch Notion, access to the Notion API was done via Notion SDK JVM, a Kotlin library that abstracts the REST communication. While it’s charming for a quick start, it has a few drawbacks:
🧵
