Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump com.google.dagger:dagger from 2.47 to 2.51 #1884

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 28, 2024

Bumps com.google.dagger:dagger from 2.47 to 2.51.

Release notes

Sourced from com.google.dagger:dagger's releases.

Dagger 2.50

Dagger

Potential breaking changes

  • Introduced a new dagger.internal.Provider to facilitate future support for jakarta.inject.Provider types. There should be no visible changes at this time, though with such a large change there is a risk of unanticipated version compatibility issues across libraries built with different Dagger versions. (75d3cbcf9)
  • Flip the default for -Adagger.explicitBindingConflictsWithInject to enabled. This flag fixes a bug where an explicit binding like an @Provides should conflict with @Inject bindings if the @Inject is actually used in a parent component. (8372c6308)

Bug fixes

  • Fixed the error message for an @Binds @IntoSet implementation with duplicate bindings. (8d0122322)

Dagger 2.49

Dagger

New features:

  • Fixed #4044: Add support for KSP with dagger.android (832717767).

Potential breaking changes:

  • Dagger’s generated component no longer contains deprecated no-op module setter methods for modules that have only static/abstract @Provides/@Binds methods (ed47d4b88).

    Note: If you hit this issue, the fix is to remove the call to the setter method in your code. For example:

    MyComponent component =
        DaggerMyComponent.builder()
    -        .moduleWithOnlyStaticOrAbstractMethods(new ModuleWithOnlyStaticOrAbstractMethods())
            .build();

    These setter methods were already no-ops (i.e. Dagger just ignored them), so removing it should not cause any functional changes.

Bug fixes:

  • Fixed #4046, #4140: Fixes Unexpected element error in when calculating nullability (4593c0a)
  • Fixed #4096: Fix type names for inline types on the KSP side (aosp/2789273)
  • Build-time performance improvements (85e9ff1) and (d9d0a8e).
  • Fixed #4060: Updated KSP to 1.9.20-1.0.14 which should contain the fix for a number of incremental processing issues related to KSP (692015f).

Hilt

New features:

  • Fixed google/dagger#2287, #3523: Add support for using @AssistedInject with @HiltViewModel. (8327177). For more details visit https://dagger.dev/hilt/view-model#assisted-injection.
  • Hilt now provides @ActivityRetainedSavedState SavedStateHandle from ActivityRetainedComponent (1cac33b). Note: This feature relies on a somewhat experimental implementation in order to provide this binding lazily while also avoiding leaking the activity. The laziness is a requirement to not restrict activity injection and also to avoid bloating the saved state when unused. While we predict this should be safe to rely on, if issues are discovered with this implementation, it is possible that a future release may have to remove this binding.

Bug fixes:

... (truncated)

Commits
  • c6c0b8a 2.51 release
  • 0786d0a Allow obfuscating @​HiltViewModel annotated ViewModel name with r8.
  • c5075df Remove kitkat-specific test.
  • c40811e Add a SkipTestInjection annotation to disable injecting the test class. This ...
  • 02d62d6 Replace processingEnv.requireTypeElement() with `DaggerSuperficialValidatio...
  • c872238 Improve Dagger error messages to give more information and be more consistent.
  • 7ac1dcc Internal changes
  • 09e5ac2 Include proguard rules in dagger core artifact so that LazyClassKeyMap's stri...
  • 348bd75 Rename proguard_specs attribute for gen_maven_artifact to reflect how it will...
  • d7a55be Migrate usages of Truth8.assertThat to equivalent usages of `Truth.assertTh...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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)

@dependabot dependabot bot requested a review from a team as a code owner February 28, 2024 00:55
@dependabot dependabot bot added chore Refactor, rename, cleanup, etc. dependencies Pull requests that update a dependency file safe-to-test labels Feb 28, 2024
@dependabot dependabot bot requested review from andrewazores, ebaron and a team February 28, 2024 00:55
@github-actions github-actions bot added the needs-triage Needs thorough attention from code reviewers label Feb 28, 2024
@dependabot dependabot bot force-pushed the dependabot/maven/com.google.dagger-dagger-2.51 branch 2 times, most recently from de74550 to dfbbb06 Compare March 1, 2024 18:04
@dependabot dependabot bot force-pushed the dependabot/maven/com.google.dagger-dagger-2.51 branch 2 times, most recently from 8c4368c to 633b06e Compare March 18, 2024 14:17
@dependabot dependabot bot force-pushed the dependabot/maven/com.google.dagger-dagger-2.51 branch 2 times, most recently from da3375a to 7d0b3e7 Compare March 19, 2024 18:41
Bumps [com.google.dagger:dagger](https://github.com/google/dagger) from 2.47 to 2.51.
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.47...dagger-2.51)

---
updated-dependencies:
- dependency-name: com.google.dagger:dagger
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/maven/com.google.dagger-dagger-2.51 branch from 7d0b3e7 to 5f310ca Compare March 27, 2024 14:38
Copy link
Contributor Author

dependabot bot commented on behalf of github Apr 1, 2024

Superseded by #1898.

@dependabot dependabot bot closed this Apr 1, 2024
@dependabot dependabot bot deleted the dependabot/maven/com.google.dagger-dagger-2.51 branch April 1, 2024 00:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Refactor, rename, cleanup, etc. dependencies Pull requests that update a dependency file needs-triage Needs thorough attention from code reviewers safe-to-test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants