chore: update dependency io.vavr:vavr to v1 #1851
Open
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.11.0→1.0.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
vavr-io/vavr (io.vavr:vavr)
v1.0.0Vavr 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.0label reflects what has been true in practice for a long time: Vavr is production-ready, stable, and not deadThank 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
TaskAPI, 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
Full Changelog: vavr-io/vavr@v0.11.0...v1.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.