Skip to content

Update dependency io.vavr:vavr to v1#3228

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/io.vavr-vavr-1.x
Open

Update dependency io.vavr:vavr to v1#3228
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/io.vavr-vavr-1.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 5, 2026

This PR contains the following updates:

Package Change Age Confidence
io.vavr:vavr (source) 0.11.01.0.1 age confidence

Release Notes

vavr-io/vavr (io.vavr:vavr)

v1.0.1

Fixes a native HashMap serialization bug, which serialized the internal HashArrayMappedTrie structure including the pre-computed hash values of keys.

For keys like enums that use Object.hashCode() (non-deterministic across JVM restarts), these stored hash values would differ in another process, causing lookups to fail.

giphy-3

Full Changelog: vavr-io/vavr@v1.0.0...v1.0.1

v1.0.0

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

Full Changelog: vavr-io/vavr@v0.11.0...v1.0.0


Configuration

📅 Schedule: Branch creation - Between 07:00 AM and 07:59 PM, only on Monday, Wednesday, and Thursday ( * 7-19 * * 1,3,4 ) in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants