Bump metro from 0.10.4 to 0.11.2

[dependabot]

Bumps metro from 0.10.4 to 0.11.2.
Updates dev.zacsweers.metro:metrox-viewmodel-compose from 0.10.4 to 0.11.2

Release notes

Sourced from dev.zacsweers.metro:metrox-viewmodel-compose's releases.

0.11.2

New

Class/KClass map key interop

This release introduces a special-cased opt-in java.lang.Class and kotlin.reflect.KClass interop on JVM/android compilations. While these types are not intrinsics of each other in regular code, they are in annotations and are often used in Map multibindings. Metro can support these if you enable the enableKClassToClassMapKeyInterop option. When enabled, java.lang.Class and kotlin.reflect.KClass are treated as interchangeable in map key types, matching Kotlin's own annotation compilation behavior. This only applies to map keys because these are the only scenario where annotation arguments are materialized into non-annotation code (i.e. @ClassKey(Foo::class) -> Map<Class<*>, V>).

This is disabled by default (even if other framework interops like includeDagger are enabled) because this is purely for annotations interop and potentially comes at some runtime overhead cost to interop since KClass types are still used under the hood and must be mapped in some cases. It's recommended to migrate these to KClass and call .java where necessary if possible.

Enhancements

• [FIR]: Report adhoc graph extension factories as these are unsupported in Metro (but apparently supported in Dagger!)
• [FIR]: Report a diagnostic error for usage of Dagger's @LazyClassKey as this is unsupported in Metro.
• [IR]: Report warning diagnostics for unused synthetic multibindings, as it's often a sign that the user accidentally bound them to the wrong supertype.

  warning: [Metro/SuspiciousUnusedMultibinding] Synthetic multibinding kotlin.collections.Map<kotlin.reflect.KClass<*>, BaseViewModel> is unused but has 4 source binding(s). Did you possibly bind them to the wrong type?
  SuspiciousUnusedMultibinding.kt:36:1
  HomeViewmodel contributes a binding of BaseViewModel
  ~~~~~~~~~~~~~
  SuspiciousUnusedMultibinding.kt:31:1
  AccountViewModel contributes a binding of BaseViewModel
  ~~~~~~~~~~~~~
  SuspiciousUnusedMultibinding.kt:26:1
  SettingsViewModel contributes a binding of BaseViewModel
  ~~~~~~~~~~~~~
  ...and 1 more
  Similar multibindings:
  
  Map<KClass<*>, ViewModel>
  

[Gradle]: Add IDE support docs link to @RequiresIdeSupport opt-in message.

Fixes

• [IR]: Fix a code gen bug where @Provides graph parameters wouldn't correctly be used by scoped bindings directly held in that graph.

Contributors

Special thanks to the following contributors for contributing to this release!

• @​inorichi
• @​jonapoul

What's Changed

• Add docs link to @RequiresIdeSupport warning by @​jonapoul in ZacSweers/metro#1916
• Update GitHub Artifact Actions (major) by @​renovate[bot] in ZacSweers/metro#1917
• Update timestamps on ide caches to prevent re-downloads by @​ZacSweers in ZacSweers/metro#1918
• Report adhoc graph extension factories by @​ZacSweers in ZacSweers/metro#1897
• Report warning diagnostics for unused synthetic multibindings by @​ZacSweers in ZacSweers/metro#1919

... (truncated)

Changelog

Sourced from dev.zacsweers.metro:metrox-viewmodel-compose's changelog.

0.11.2

2026-03-02

New

Class/KClass map key interop

This release introduces a special-cased opt-in java.lang.Class and kotlin.reflect.KClass interop on JVM/android compilations. While these types are not intrinsics of each other in regular code, they are in annotations and are often used in Map multibindings. Metro can support these if you enable the enableKClassToClassMapKeyInterop option. When enabled, java.lang.Class and kotlin.reflect.KClass are treated as interchangeable in map key types, matching Kotlin's own annotation compilation behavior. This only applies to map keys because these are the only scenario where annotation arguments are materialized into non-annotation code (i.e. @ClassKey(Foo::class) -> Map<Class<*>, V>).

This is disabled by default (even if other framework interops like includeDagger are enabled) because this is purely for annotations interop and potentially comes at some runtime overhead cost to interop since KClass types are still used under the hood and must be mapped in some cases. It's recommended to migrate these to KClass and call .java where necessary if possible.

Enhancements

• [FIR]: Report adhoc graph extension factories as these are unsupported in Metro (but apparently supported in Dagger!)
• [FIR]: Report a diagnostic error for usage of Dagger's @LazyClassKey as this is unsupported in Metro.
• [IR]: Report warning diagnostics for unused synthetic multibindings, as it's often a sign that the user accidentally bound them to the wrong supertype.

  warning: [Metro/SuspiciousUnusedMultibinding] Synthetic multibinding kotlin.collections.Map<kotlin.reflect.KClass<*>, BaseViewModel> is unused but has 4 source binding(s). Did you possibly bind them to the wrong type?
  SuspiciousUnusedMultibinding.kt:36:1
  HomeViewmodel contributes a binding of BaseViewModel
  ~~~~~~~~~~~~~
  SuspiciousUnusedMultibinding.kt:31:1
  AccountViewModel contributes a binding of BaseViewModel
  ~~~~~~~~~~~~~
  SuspiciousUnusedMultibinding.kt:26:1
  SettingsViewModel contributes a binding of BaseViewModel
  ~~~~~~~~~~~~~
  ...and 1 more
  Similar multibindings:
  
  Map<KClass<*>, ViewModel>
  

[Gradle]: Add IDE support docs link to @RequiresIdeSupport opt-in message.

Fixes

• [IR]: Fix a code gen bug where @Provides graph parameters wouldn't correctly be used by scoped bindings directly held in that graph.

Contributors

Special thanks to the following contributors for contributing to this release!

• @​inorichi
• @​jonapoul

0.11.1

... (truncated)

Commits

• 762fa70 Prepare for release 0.11.2.
• f6766a4 Include similar bindings when reporting suspicious unused multis (#1930)
• c55af9e CHANGELOG formatting
• ed645ef Report diagnostic for LazyClassKey (#1929)
• 65d4b39 Update plugin shadow to v9.3.2 (#1927)
• 7ca9bb3 Add test to reproduce ClassCastException when using SingleIn graphs into grap...
• e85c915 Add KClass/Class interop for map keys (#1926)
• e47763b Update poko to v0.21.2 (#1925)
• d438b2f Fix FIR factory gen using wrong owner (#1924)
• ba653c1 Update Gradle to v9.4.0-rc-2 (#1922)
• Additional commits viewable in compare view

Updates dev.zacsweers.metro from 0.10.4 to 0.11.2

Release notes

Sourced from dev.zacsweers.metro's releases.

0.11.2

New

Class/KClass map key interop

This release introduces a special-cased opt-in java.lang.Class and kotlin.reflect.KClass interop on JVM/android compilations. While these types are not intrinsics of each other in regular code, they are in annotations and are often used in Map multibindings. Metro can support these if you enable the enableKClassToClassMapKeyInterop option. When enabled, java.lang.Class and kotlin.reflect.KClass are treated as interchangeable in map key types, matching Kotlin's own annotation compilation behavior. This only applies to map keys because these are the only scenario where annotation arguments are materialized into non-annotation code (i.e. @ClassKey(Foo::class) -> Map<Class<*>, V>).

This is disabled by default (even if other framework interops like includeDagger are enabled) because this is purely for annotations interop and potentially comes at some runtime overhead cost to interop since KClass types are still used under the hood and must be mapped in some cases. It's recommended to migrate these to KClass and call .java where necessary if possible.

Enhancements

• [FIR]: Report adhoc graph extension factories as these are unsupported in Metro (but apparently supported in Dagger!)
• [FIR]: Report a diagnostic error for usage of Dagger's @LazyClassKey as this is unsupported in Metro.
• [IR]: Report warning diagnostics for unused synthetic multibindings, as it's often a sign that the user accidentally bound them to the wrong supertype.

  warning: [Metro/SuspiciousUnusedMultibinding] Synthetic multibinding kotlin.collections.Map<kotlin.reflect.KClass<*>, BaseViewModel> is unused but has 4 source binding(s). Did you possibly bind them to the wrong type?
  SuspiciousUnusedMultibinding.kt:36:1
  HomeViewmodel contributes a binding of BaseViewModel
  ~~~~~~~~~~~~~
  SuspiciousUnusedMultibinding.kt:31:1
  AccountViewModel contributes a binding of BaseViewModel
  ~~~~~~~~~~~~~
  SuspiciousUnusedMultibinding.kt:26:1
  SettingsViewModel contributes a binding of BaseViewModel
  ~~~~~~~~~~~~~
  ...and 1 more
  Similar multibindings:
  
  Map<KClass<*>, ViewModel>
  

[Gradle]: Add IDE support docs link to @RequiresIdeSupport opt-in message.

Fixes

• [IR]: Fix a code gen bug where @Provides graph parameters wouldn't correctly be used by scoped bindings directly held in that graph.

Contributors

Special thanks to the following contributors for contributing to this release!

• @​inorichi
• @​jonapoul

What's Changed

• Add docs link to @RequiresIdeSupport warning by @​jonapoul in ZacSweers/metro#1916
• Update GitHub Artifact Actions (major) by @​renovate[bot] in ZacSweers/metro#1917
• Update timestamps on ide caches to prevent re-downloads by @​ZacSweers in ZacSweers/metro#1918
• Report adhoc graph extension factories by @​ZacSweers in ZacSweers/metro#1897
• Report warning diagnostics for unused synthetic multibindings by @​ZacSweers in ZacSweers/metro#1919

... (truncated)

Changelog

Sourced from dev.zacsweers.metro's changelog.

0.11.2

2026-03-02

New

Class/KClass map key interop

This release introduces a special-cased opt-in java.lang.Class and kotlin.reflect.KClass interop on JVM/android compilations. While these types are not intrinsics of each other in regular code, they are in annotations and are often used in Map multibindings. Metro can support these if you enable the enableKClassToClassMapKeyInterop option. When enabled, java.lang.Class and kotlin.reflect.KClass are treated as interchangeable in map key types, matching Kotlin's own annotation compilation behavior. This only applies to map keys because these are the only scenario where annotation arguments are materialized into non-annotation code (i.e. @ClassKey(Foo::class) -> Map<Class<*>, V>).

This is disabled by default (even if other framework interops like includeDagger are enabled) because this is purely for annotations interop and potentially comes at some runtime overhead cost to interop since KClass types are still used under the hood and must be mapped in some cases. It's recommended to migrate these to KClass and call .java where necessary if possible.

Enhancements

• [FIR]: Report adhoc graph extension factories as these are unsupported in Metro (but apparently supported in Dagger!)
• [FIR]: Report a diagnostic error for usage of Dagger's @LazyClassKey as this is unsupported in Metro.
• [IR]: Report warning diagnostics for unused synthetic multibindings, as it's often a sign that the user accidentally bound them to the wrong supertype.

  warning: [Metro/SuspiciousUnusedMultibinding] Synthetic multibinding kotlin.collections.Map<kotlin.reflect.KClass<*>, BaseViewModel> is unused but has 4 source binding(s). Did you possibly bind them to the wrong type?
  SuspiciousUnusedMultibinding.kt:36:1
  HomeViewmodel contributes a binding of BaseViewModel
  ~~~~~~~~~~~~~
  SuspiciousUnusedMultibinding.kt:31:1
  AccountViewModel contributes a binding of BaseViewModel
  ~~~~~~~~~~~~~
  SuspiciousUnusedMultibinding.kt:26:1
  SettingsViewModel contributes a binding of BaseViewModel
  ~~~~~~~~~~~~~
  ...and 1 more
  Similar multibindings:
  
  Map<KClass<*>, ViewModel>
  

[Gradle]: Add IDE support docs link to @RequiresIdeSupport opt-in message.

Fixes

• [IR]: Fix a code gen bug where @Provides graph parameters wouldn't correctly be used by scoped bindings directly held in that graph.

Contributors

Special thanks to the following contributors for contributing to this release!

• @​inorichi
• @​jonapoul

0.11.1

... (truncated)

Commits

• 762fa70 Prepare for release 0.11.2.
• f6766a4 Include similar bindings when reporting suspicious unused multis (#1930)
• c55af9e CHANGELOG formatting
• ed645ef Report diagnostic for LazyClassKey (#1929)
• 65d4b39 Update plugin shadow to v9.3.2 (#1927)
• 7ca9bb3 Add test to reproduce ClassCastException when using SingleIn graphs into grap...
• e85c915 Add KClass/Class interop for map keys (#1926)
• e47763b Update poko to v0.21.2 (#1925)
• d438b2f Fix FIR factory gen using wrong owner (#1924)
• ba653c1 Update Gradle to v9.4.0-rc-2 (#1922)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[bherbst]

@dependabot rebase