chore(deps): Update immutables to v2.11.4 #96
Merged
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.
Note
Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to
mend[bot].This notice will be removed on 2025-10-07.
This PR contains the following updates:
2.11.1->2.11.42.11.1->2.11.4Release Notes
immutables/immutables (org.immutables:annotate)
v2.11.4Compare Source
Maintenance & refinements release
Thank you for the bug reports and PRs!
Issues
@Value.Default.{Int, Long, String...}were always applied for Immutable values (were ok for records)$and_in java identifiers in import rewriter)-Aimmutables.annotation=<fqcn>for custom annotation (can have meta-styles etc)PRs
New Contributors
Full Changelog: immutables/immutables@2.11.3...2.11.4
v2.11.3Compare Source
Maintenance & refinements release
Thank you for PRs and providing feedback!
@Value.Default, no warnings are issued.What's Changed
Full Changelog: immutables/immutables@2.11.2...2.11.3
v2.11.2Compare Source
Maintenance and refinement release
frommerging method for many supertypesfromsupertypes. Switch viaStyle.mergeFromSupertypesDynamically=false. This gives (very) old behavior before dynamic merging was introduced, for some, it is more intuitive than dynamic logic and avoid heap pollution (& ClassCastException) for some rare cases of supertypes imlementing parameterized interfaces with different actual type arguments in a hierarchy.required=falsewas generated only for Nullable, now - for any non mandatory attribute). Generating Jacksonrequiredcan be disabled viasetJacksonPropertyRequired=false, the difference is if Jackson will issue an error on missing attribute or Immutables' builder will throw an exception for the same.PRs merged
New Contributors
Full Changelog: immutables/immutables@2.11.1...2.11.2
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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.