Vavr started in 2014 as Javaslang, a small experiment in bringing functional programming to Java. Over the years, it grew into a comprehensive library trusted by thousands of projects.
This is the first* stable major release. It marks the point where the API is mature, battle-tested, and ready for long-term production use with full semantic versioning guarantees going forward. Vavr 1.0.0 is intentionally not a revolution. The goal of this release is to formalize the stability that 0.x users have relied on for years, not to reinvent the library.
The 1.0.0 label reflects what has been true in practice for a long time: Vavr is production-ready, stable, and not dead
Thank you to every contributor who filed issues, submitted pull requests, improved documentation, and helped shape the library over the past 12 years.
Philosophy of 1.0.0
1.0.0 is a drop-in replacement for 0.11.0. The API you know is the API you get. If your project compiles against 0.11.0, upgrading to 1.0.0 should be a version bump and nothing more (unless you used the experimental Task API, which was the only removal).
Larger changes - such as an aggressive minimum Java version bump, potential API redesigns, and leveraging modern JVM features - are deliberately staged for Vavr 2.x. The 1.0.0 line will remain a conservative, Java 8-compatible foundation for projects that need long-term stability above all else.
What's Changed
- Fix: Missing .mapTo / .mapToVoid override on Either by @adamkopec (#3218)
- hundreds of tiny JavaDocs issues by @pivovarit
Full Changelog: v0.11.0...v1.0.0