-
Notifications
You must be signed in to change notification settings - Fork 131
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.33 #3692
Conversation
Generated by 🚫 dangerJS |
6f73222
to
27f0725
Compare
You can test the changes on this Pull Request by downloading the APK here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM. CI is green.
It's the first time that I see a Dependabot PR that touches the the login library.
Because of the (broken) Git subtree approach, changes done to the login library from Woo or WordPress need to be manually ported back to the source repo (e.g. see this recent PR).
Should we do this now, or wait till a new source change comes around and bring this along with it?
The composite build work will sort all of this out by letting us have the best of both world: fast feedback when editing the libraries locally and dedicated projects for each library.
Following up on my previous comment regarding manual updates to the login library, it looks like Dependabot's really onto it with at least another PR opened (and merged) to bump a dependency. Taking that into account, I think it manually porting each update to the libraries manually would be too much overhead. I'm happy to stick to the current "whenever needed" approach. Another option could be to have a recurring task (weekly, fortnightly?) to batch-port version bumps. Hopefully it won't be long till we implement the composite build workflow here and remove the need for this in the first place 👍 Leaving this still not merged to hear what other folks have to say. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it manually porting each update to the libraries manually would be too much overhead. I'm happy to stick to the current "whenever needed" approach.
True, I vote for choosing "whenever needed" approach.
Similar case (but without git subtree case) raised with #3688 and FluxC
library and was discussed here: p1615911957028000-slack-C70PAM3RA We ended up merging dependency bump.
Just as a side note:
This LGTM. CI is green.
That's why I really like Dagger
. Because of build-time generated code we can be quite safe - any crashes shouldn't raise in the runtime.
27f0725
to
e74b8a3
Compare
Bumps `daggerVersion` from 2.29.1 to 2.33. Updates `dagger` from 2.29.1 to 2.33 - [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.33) Updates `dagger-compiler` from 2.29.1 to 2.33 - [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.33) Updates `dagger-android-support` from 2.29.1 to 2.33 - [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.33) Updates `dagger-android-processor` from 2.29.1 to 2.33 - [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.33) Signed-off-by: dependabot[bot] <support@github.com>
e74b8a3
to
b3c9a1c
Compare
Thanks for the input @wzieba! |
Bumps
daggerVersion
from 2.29.1 to 2.33.Updates
dagger
from 2.29.1 to 2.33Release notes
Sourced from dagger's releases.
... (truncated)
Commits
ae991fd
2.33 release78438d5
Update all "alpha" references to "beta" in preparation for the upcoming beta ...ceccfc6
Add job to GitHub Actions to validate the Dagger version.8a4b7e2
Remove cache of top level component implementations8a92723
Fixes to javadoc and links for EarlyEntryPoint5877be8
Add internal utility method.1ad74b9
Follow-up changes to the EarlyEntryPoint API289f59f
Add EarlyTestEntryPoints to allow entry points to be called in tests before t...608e6cc
Remove a comment that seems to be left around from Ahead-of-time Subcomponent...73628bc
Enable remaining dagger.android and dagger.hilt tests.Updates
dagger-compiler
from 2.29.1 to 2.33Release notes
Sourced from dagger-compiler's releases.
... (truncated)
Commits
ae991fd
2.33 release78438d5
Update all "alpha" references to "beta" in preparation for the upcoming beta ...ceccfc6
Add job to GitHub Actions to validate the Dagger version.8a4b7e2
Remove cache of top level component implementations8a92723
Fixes to javadoc and links for EarlyEntryPoint5877be8
Add internal utility method.1ad74b9
Follow-up changes to the EarlyEntryPoint API289f59f
Add EarlyTestEntryPoints to allow entry points to be called in tests before t...608e6cc
Remove a comment that seems to be left around from Ahead-of-time Subcomponent...73628bc
Enable remaining dagger.android and dagger.hilt tests.Updates
dagger-android-support
from 2.29.1 to 2.33Release notes
Sourced from dagger-android-support's releases.
... (truncated)
Commits
ae991fd
2.33 release78438d5
Update all "alpha" references to "beta" in preparation for the upcoming beta ...ceccfc6
Add job to GitHub Actions to validate the Dagger version.8a4b7e2
Remove cache of top level component implementations8a92723
Fixes to javadoc and links for EarlyEntryPoint5877be8
Add internal utility method.1ad74b9
Follow-up changes to the EarlyEntryPoint API289f59f
Add EarlyTestEntryPoints to allow entry points to be called in tests before t...608e6cc
Remove a comment that seems to be left around from Ahead-of-time Subcomponent...73628bc
Enable remaining dagger.android and dagger.hilt tests.Updates
dagger-android-processor
from 2.29.1 to 2.33Release notes
Sourced from dagger-android-processor's releases.
... (truncated)
Commits
ae991fd
2.33 release78438d5
Update all "alpha" references to "beta" in preparation for the upcoming beta ...ceccfc6
Add job to GitHub Actions to validate the Dagger version.8a4b7e2
Remove cache of top level component implementations8a92723
Fixes to javadoc and links for EarlyEntryPoint5877be8
Add internal utility method.1ad74b9
Follow-up changes to the EarlyEntryPoint API289f59f
Add EarlyTestEntryPoints to allow entry points to be called in tests before t...608e6cc
Remove a comment that seems to be left around from Ahead-of-time Subcomponent...73628bc
Enable remaining dagger.android and dagger.hilt tests.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