-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[webview]: Bump androidx.webkit:webkit from 1.12.0 to 1.12.1 in /packages/webview_flutter/webview_flutter_android/android #7801
Conversation
Bumps androidx.webkit:webkit from 1.12.0 to 1.12.1. --- updated-dependencies: - dependency-name: androidx.webkit:webkit dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
It looks like this bump requires bumping the minSdkVersion to 21 from 19:
This is just a minor version bump for webkit and doesn't seem to have any major changes to it: https://developer.android.com/jetpack/androidx/releases/webkit#1.12.1. @flutter/android-reviewers Do you have any objections to bumping this plugin to minSdkVersion of 21? |
I think flutter only supports 21+ at this point |
No objections. |
…adle/packages/webview_flutter/webview_flutter_android/android/androidx.webkit-webkit-1.12.1
…adle/packages/webview_flutter/webview_flutter_android/android/androidx.webkit-webkit-1.12.1
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.
LGTM
## 4.0.0 | ||
|
||
* Bumps androidx.webkit:webkit from 1.12.0 to 1.12.1. | ||
* **Breaking Change** Bumps Android `minSdkVersion` from 19 to 21. |
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 thought we were going to do this as a minor version because this isn't actually breaking, since Flutter 3.24 requires 21+, so nobody should be able to be broken by this.
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.
Ah I thought that only applied to webview_flutter
. And we would make this a breaking change for the plugin.
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.
Sorry I should have gotten an additional review for clarification. Will this bump cause conflicts and do we need to revert the publish?
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.
It's going to make things unnecessarily difficult for anyone doing https://pub.dev/packages/webview_flutter#platform-specific-features because they will get resolver errors the next time they try to update webview_flutter
, and will have to figure out they need to update their webview_flutter_android
major version.
Withdrawing the published version would create a problem for us later when we actually want to bump the major version again, so I think we'll just have to live with the added friction for people with dependencies on the platform version.
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.
Ah ok now I understand. I forgot that the platform dependencies are explicitly used for platform specific features. Could we change the depdendency in webview_flutter
to >=3.16.0 <5.0.0
temporarily? Or are we better off just setting it to ^4.0.0 with the friction.
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.
That would just kick the can down the road very slightly, because the next time any feature is added we'll have to update the minimum endorsed versions to pick up the feature. Better to just get it out of the way now, rather than make the next feature update slightly more complex.
…1 in /packages/webview_flutter/webview_flutter_android/android (flutter/packages#7801)
flutter/packages@f1a3da2...67401e1 2024-10-10 [email protected] Roll Flutter from 2d45fb3 to 6790525 (7 revisions) (flutter/packages#7843) 2024-10-10 [email protected] [webview_flutter] Updates minimum supported `webview_flutter_android` from 3.16.0 to 4.0.0 (flutter/packages#7844) 2024-10-10 49699333+dependabot[bot]@users.noreply.github.com [webview]: Bump androidx.webkit:webkit from 1.12.0 to 1.12.1 in /packages/webview_flutter/webview_flutter_android/android (flutter/packages#7801) 2024-10-10 [email protected] [interactive_media_ads] Fixes bug where Android would show the last frame of the previous Ad before playing the current one (flutter/packages#7835) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC [email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Bumps androidx.webkit:webkit from 1.12.0 to 1.12.1.
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)