chore(deps): Update immutables monorepo to v2.11.3 #191
  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:
2.10.1->2.11.32.10.1->2.11.3Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
immutables/immutables (org.immutables:value)
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
v2.11.1Compare Source
Maintenance and minor enhancements
static class Builder extends MyRecordBuilder {}*IsSetmethods on builderorg.immutables:datatype. It's slightly modernized version oforg.immutables:data(now deprecated), no dependency on Guava, + support for records with generated buildersAlso
New Contributors
Full Changelog: immutables/immutables@2.11.0...2.11.1
v2.11.0Compare Source
Many thanks to all contributors: PRs, testing and evaluation much appreciated!
@Value.Builderfor records on builders@Value.Default.*annotation for constant default values for records and regular abstract types@Value.Builder record A(int a, String b) implements WithA {..@Nullablesupport in@NullMarkedmode.TYPE_USEannotations (as far as compiler and peculiarities of existing code allows),Style.attributeBuilderDetection=true:builder.value(b -> b.a(1).c(""))Also
Closed issues https://github.com/immutables/immutables/milestone/82?closed=1
New Contributors
Full Changelog: immutables/immutables@2.10.1...2.11.0
Configuration
📅 Schedule: Branch creation - "after 5pm on the 2nd day of the month" (UTC), 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.