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

Bump daggerVersion from 2.29.1 to 2.30 #352

Merged
merged 1 commit into from
Nov 23, 2020

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 23, 2020

Bumps daggerVersion from 2.29.1 to 2.30.
Updates dagger-compiler from 2.29.1 to 2.30

Release notes

Sourced from dagger-compiler's releases.

Dagger 2.30

What’s new

Hilt

Hilt has deprecated ApplicationComponent (6313cbdf2), and it will soon be removed in a future release. Use SingletonComponent instead.

Hilt now supports @BindValue val fields in Kotlin without the use of @JvmField (802882dd4). For example:

// Before
@BindValue @JvmField val bindStr = "STRING_BINDING"
// Now
@BindValue val bindStr = "STRING_BINDING"

Dagger

Dagger now uses the “experimentalDaggerErrorMessages” by default (See #1769 for more information). The old error message format can still be used by setting -Adagger.experimentalDaggerErrorMessages=disabled as a javacopt.

Bug Fixes

  • [Dagger]: Fixes a Dagger compiler crash that occurred when an @Inject was placed in a Kotlin object class. (0816c43f5)
  • [Hilt]: Fixes #2156: Update Dagger's androidx dependencies to the latest stable versions. (deff5e59e)
  • [Hilt]: Fixes suppress deprecation warning in Hilt generated Fragment class. (0a463eb84)
  • [Hilt]: Removes Hilt's dependency on jsr250 for @Generated. (8dca74b) Note: Hilt previously depended on jsr250 for the @Generated annotation, but this behavior has now been changed to match Dagger (see #95). Now, Hilt only adds the @Generated annotation only if the Generated class is present in the classpath. Thus, since we’ve now removed the jsr250 dependency from Hilt, the generated code will no longer contain the @Generated annotation by default.
Commits
  • 2b229c4 2.30 release
  • 8dca74b Remove erroneously added JSR250 deps from the Hilt runtime.
  • 6313cbd Deprecate ApplicationComponent for SingletonComponent.
  • 0e8f761 Turn on experimental dagger error messages by default. The old messages can s...
  • 55c06b5 Internal refactor.
  • 8cafe80 Rollback of Migrating @ViewModelInject into Hilt's codebase.
  • b02960c Migrating @ViewModelInject into Hilt's codebase.
  • c539b38 Internal refactor
  • a17a6e6 Don't reference the error message string in generated code. Previous post-opt...
  • deff5e5 Update Dagger's androidx dependencies to the latest stable versions.
  • Additional commits viewable in compare view

Updates dagger from 2.29.1 to 2.30

Release notes

Sourced from dagger's releases.

Dagger 2.30

What’s new

Hilt

Hilt has deprecated ApplicationComponent (6313cbdf2), and it will soon be removed in a future release. Use SingletonComponent instead.

Hilt now supports @BindValue val fields in Kotlin without the use of @JvmField (802882dd4). For example:

// Before
@BindValue @JvmField val bindStr = "STRING_BINDING"
// Now
@BindValue val bindStr = "STRING_BINDING"

Dagger

Dagger now uses the “experimentalDaggerErrorMessages” by default (See #1769 for more information). The old error message format can still be used by setting -Adagger.experimentalDaggerErrorMessages=disabled as a javacopt.

Bug Fixes

  • [Dagger]: Fixes a Dagger compiler crash that occurred when an @Inject was placed in a Kotlin object class. (0816c43f5)
  • [Hilt]: Fixes #2156: Update Dagger's androidx dependencies to the latest stable versions. (deff5e59e)
  • [Hilt]: Fixes suppress deprecation warning in Hilt generated Fragment class. (0a463eb84)
  • [Hilt]: Removes Hilt's dependency on jsr250 for @Generated. (8dca74b) Note: Hilt previously depended on jsr250 for the @Generated annotation, but this behavior has now been changed to match Dagger (see #95). Now, Hilt only adds the @Generated annotation only if the Generated class is present in the classpath. Thus, since we’ve now removed the jsr250 dependency from Hilt, the generated code will no longer contain the @Generated annotation by default.
Commits
  • 2b229c4 2.30 release
  • 8dca74b Remove erroneously added JSR250 deps from the Hilt runtime.
  • 6313cbd Deprecate ApplicationComponent for SingletonComponent.
  • 0e8f761 Turn on experimental dagger error messages by default. The old messages can s...
  • 55c06b5 Internal refactor.
  • 8cafe80 Rollback of Migrating @ViewModelInject into Hilt's codebase.
  • b02960c Migrating @ViewModelInject into Hilt's codebase.
  • c539b38 Internal refactor
  • a17a6e6 Don't reference the error message string in generated code. Previous post-opt...
  • deff5e5 Update Dagger's androidx dependencies to the latest stable versions.
  • Additional commits viewable in compare view

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 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 added the dependencies Pull requests that update a dependency file label Nov 23, 2020
Bumps `daggerVersion` from 2.29.1 to 2.30.

Updates `dagger-compiler` from 2.29.1 to 2.30
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.29.1...dagger-2.30)

Updates `dagger` from 2.29.1 to 2.30
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.29.1...dagger-2.30)

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/gradle/daggerVersion-2.30 branch from 23940f5 to c6f2600 Compare November 23, 2020 08:39
@jraska jraska merged commit 5c83120 into master Nov 23, 2020
@jraska jraska deleted the dependabot/gradle/daggerVersion-2.30 branch November 23, 2020 09:01
@jraska jraska added this to the 0.22.1 milestone Mar 19, 2021
@jraska
Copy link
Owner

jraska commented Mar 19, 2021

This PR was released with 0.22.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant