-
Notifications
You must be signed in to change notification settings - Fork 9.8k
[flutter_webview] Raise min Flutter SDK to stable #2425
Conversation
@mklim Do you think major SDK bumps warrant a major version bump (e.g. |
A few more things we should probably do flutter/flutter#47153 (comment) |
@ened I was wondering that too. The semver spec says no:
Since pub should be resolving Flutter SDK dependencies normally I think it makes sense to follow semver here. All the actual changes in this amount to internal refactoring so I kept it as a patch bump. @xster good catch, marking this as a WIP until I resolve those other steps. |
v2 embedding apps no longer need to special case their Flutter SDK requirement like they have since v0.3.15+3.
OK, this should be ready for review now. |
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
Sorry, I can't find a comment about this there. @blasten or @xster do you mind copy pasting it? I don't think this should break anyone on 1.9, because it's bumping the minimum Flutter SDK version in the |
ya I deleted the comment and hoped it's forever erased from everyone's memory after typing it and realizing that it's no long valid since we moved the sdk restriction up :) |
Lol all good, thanks. :) |
* [google_sign_in] Pass the client id to the platform interface. (flutter#2427) The param exists in the platform interface but there was no way to pass anything to clientId through the external interface. * [in_app_purchase]Change a comment. (flutter#2329) * re-enable stable CI (flutter#2402) * [flutter_webview] Raise min Flutter SDK to stable (flutter#2425) v2 embedding apps no longer need to special case their Flutter SDK requirement like they have since v0.3.15+3. * [battery] cleanup for Android embedding post 1.12 (flutter#2400) * [google_sign_in] Expose network error (flutter#2398)
v2 embedding apps no longer need to special case their Flutter SDK requirement like they have since v0.3.15+3.
…acheing-01-08 * flutterPlugin/master: (30 commits) Update Gradle version (flutter#2448) [image_picker] support android V2 embedding (flutter#2430) [webview_flutter] Setup XCTests (flutter#2445) [video_player] Fixes video initialization future stall. (flutter#2134) [ci] Upgrade to Xcode 11.3 (flutter#2435) [In_app_purchases] migrate to Play Billing Library 2.0. (flutter#2287) Migrate away from deprecated `BinaryMessages` (flutter#2444) [google_sign_in]Update google_sign_in_example name in pubspec.yaml (flutter#2335) [ios_platform_images] Removed android support from the pubspec. (flutter#2432) [google_sign_in] Expose network error (flutter#2398) [battery] cleanup for Android embedding post 1.12 (flutter#2400) [flutter_webview] Raise min Flutter SDK to stable (flutter#2425) re-enable stable CI (flutter#2402) [in_app_purchase]Change a comment. (flutter#2329) [google_sign_in] Pass the client id to the platform interface. (flutter#2427) [ios_platform_images] Made ios_platform_images set the correct image scale. (flutter#2414) [url_launcher_platform_interface] use non static token for platform interface (flutter#2418) [plugin_platform_interface] Don't use const Object as a token (flutter#2417) Update endorsed macos plugins readme and update others (flutter#2407) [webview_flutter] add gesture navigation for iOS (flutter#2339) ... # Conflicts: # packages/video_player/video_player/CHANGELOG.md # packages/video_player/video_player/pubspec.yaml
…)" This reverts commit 2be4c80.
v2 embedding apps no longer need to special case their Flutter SDK requirement like they have since v0.3.15+3.
Description
v2 embedding apps no longer need to special case their Flutter SDK
requirement like they have since v0.3.15+3.
Related Issues
flutter/flutter#47153
flutter/flutter#42348
flutter/flutter#42694
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]
). This will ensure a smooth and quick review process.///
).flutter analyze
) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?