Conversation
fluttergithubbot
added
tool
flutter-dashboard
bot
added
c: contributor-productivity
auto-submit
bot
removed
the
autosubmit
|
auto label is removed for flutter/flutter, pr: 121847, due to - Please get at least one approved review if you are already a member or two member reviews if you are not a member before re-applying this label. Reviewers: If you left a comment approving, please use the "approve" review action instead. |
|
auto label is removed for flutter/flutter, pr: 121847, due to Validations Fail. |
christopherfujino
added
the
autosubmit
auto-submit
bot
removed
the
autosubmit
|
auto label is removed for flutter/flutter, pr: 121847, due to - The status or check suite Mac tool_integration_tests_4_4 has failed. Please fix the issues identified (or deflake) before re-applying this label. |
| collection: 1.17.1 # THIS LINE IS AUTOGENERATED - TO UPDATE USE "flutter update-packages --force-upgrade" | ||
| cross_file: 0.3.3+4 # THIS LINE IS AUTOGENERATED - TO UPDATE USE "flutter update-packages --force-upgrade" | ||
| flutter_plugin_android_lifecycle: 2.0.8 # THIS LINE IS AUTOGENERATED - TO UPDATE USE "flutter update-packages --force-upgrade" | ||
| flutter_plugin_android_lifecycle: 2.0.9 # THIS LINE IS AUTOGENERATED - TO UPDATE USE "flutter update-packages --force-upgrade" |
There was a problem hiding this comment.
@reidbaker could you take a look at this? This change appears to be causing the following failure (although I can't explain why it seems to have passed on Linux...)
[ ] Cause 1: org.gradle.internal.resolve.ModuleVersionResolveException: Could not resolve androidx.annotation:annotation:1.5.0.
[ ] Required by:
[ ] project :flutter_plugin_android_lifecycle
Here is the changelog for this plugin: https://github.com/flutter/packages/commits/main/packages/flutter_plugin_android_lifecycle
There was a problem hiding this comment.
|
The package that broke CI was manually pinned, so closing this |
Unpins flutter_plugin_android_lifecycle where it is pinned. I then 1. ran `flutter update-packages --force-upgrade` (but only committed the changes within `dev/integration_tests/gradle_deprecated_settings/`, which is where it had been pinned) 2. followed by `./gradlew :generateLockfiles` from `dev/integration_tests/gradle_deprecated_settings/android/` (the lockfile was what was causing the CI dependency resolution failure, so this second step is the fix for that). See the reason it was pinned: #121847 (comment) followed by the PR that pinned it: #122043 Fixes #122039
2 participants
This PR was generated by
flutter update-packages --force-upgrade.