mirror of
https://github.com/flutter/packages.git
synced 2025-08-06 08:53:11 +08:00
7384 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
| 44ee590f33 |
[ci] Run Swift formatter and linter during CI formatting (#5928)
Make `swift-format` CIPD package available on the `PATH` https://flutter-review.googlesource.com/c/recipes/+/54020 Run `format --no-clang-format --no-java --no-kotlin --no-dart` on the macOS builder so it doesn't duplicate same `format` call run on Linux. Filter out generated files until https://github.com/flutter/flutter/issues/141799 is done. Also add `swift-format lint` call during `format` command. Fix the one casing issue it found in a test file. Failing run: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8758535881172004177/+/u/Run_package_tests/Swift_format/stdout Successful run: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8758492350529121249/+/u/Run_package_tests/Swift_format/stdout Fixes https://github.com/flutter/flutter/issues/41129 |
|||
| bb9be73e42 |
Manual roll Flutter from f77f82435a97 to 684247a3c78a (39 revisions) (#5948)
Manual roll Flutter from f77f82435a97 to 684247a3c78a (39 revisions)
Manual roll requested by dit@google.com
|
|||
| 7901015fa4 |
Expose registered widget libraries and local widget library widgets. (#5936)
This exposes the necessary information to allow rfwpg to display registered libraries and widgets in a list or tree.rfw-v1.0.18 |
|||
| da6d872199 |
Bump actions/upload-artifact from 4.1.0 to 4.2.0 (#5937)
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4.1.0 to 4.2.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/upload-artifact/releases">actions/upload-artifact's releases</a>.</em></p> <blockquote> <h2>v4.2.0</h2> <h2>What's Changed</h2> <ul> <li>Ability to overwrite an Artifact by <a href="https://github.com/robherley"><code>@ârobherley</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/501">actions/upload-artifact#501</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/upload-artifact/compare/v4...v4.2.0">https://github.com/actions/upload-artifact/compare/v4...v4.2.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
|||
| 137149158c |
Manual roll Flutter (stable) from ef1af02aead6 to 67457e669f79 (1 revision) (#5932)
Manual roll requested by dit@google.com
|
|||
| 129e08c1df |
[pigeon] Run swift-format on ungenerated example app Swift files (#5934)
Run `swift-format` linter/formatter on Swift files in example apps. This only touches Swift files in example/test code. This also doesn't format any autogenerated Swift files, which would require changed in the pigeon generator: https://github.com/flutter/flutter/issues/141799 Part of turning on swift-format CI formatting https://github.com/flutter/packages/pull/5928 |
|||
| 9379e4ab01 |
[path_provider_foundation] Run swift-format on Swift files (#5935)
Run `swift-format` linter/formatter on Swift files. Part of turning on swift-format CI formatting https://github.com/flutter/packages/pull/5928 |
|||
| 76a6fd20f0 |
[shared_preferences_foundation] Run swift-format on Swift files (#5933)
Run `swift-format` linter/formatter on Swift files. Part of turning on swift-format CI formatting https://github.com/flutter/packages/pull/5928 |
|||
| 4dd91ce86f |
[various] Run swift-format on example app Swift files (#5931)
Run `swift-format` linter/formatter on Swift files in example apps. This doesn't touch any Swift files in non-example code. Part of turning on swift-format CI formatting https://github.com/flutter/packages/pull/5928 |
|||
| 1ccc0e1749 |
[camera_avfoundation] Remove development team from Xcode example app (#5930)
`DEVELOPMENT_TEAM` should not be set in the example Xcode app. Introduced extraneously in #3272 |
|||
| 2762c54446 |
[webview_flutter_wkwebview] Add javascript panel interface for wkwebview (#5795)
* There are cases where Web calls System Popup with javascript on webview_flutter * At this time, the message comes in the WKUIDelegate part in iOS. * https://developer.apple.com/documentation/webkit/wkuidelegate/1537406-webview * https://developer.apple.com/documentation/webkit/wkuidelegate/1536489-webview * Related issue: https://github.com/flutter/flutter/issues/30358#issuecomment-1645347616 * Related Interface PR: https://github.com/flutter/packages/pull/5670 * The PR that contains all changes can be found at https://github.com/flutter/packages/pull/4704webview_flutter_wkwebview-v3.11.0 |
|||
| a5dbf451a6 |
[two_dimensional_scrollables] Fix must_call_super (#5921)
This would fix the analyzer error for `two_dimensional_scrollables` after merging the https://github.com/flutter/flutter/pull/141504.two_dimensional_scrollables-v0.0.5+2 |
|||
| 3e7d502127 |
[pointer_interceptor] fix width and height unset warning on web platform (#5864)
This PR adds width/height to the dom element created by the default factory to prevent the framework from screaming at usages of this plugin.
Needed until this bit becomes `stable`:
*
pointer_interceptor_web-v0.10.1+2
|
|||
| 39ffed30e6 |
Bump github/codeql-action from 3.23.0 to 3.23.1 (#5922)
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.23.0 to 3.23.1. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/github/codeql-action/blob/main/CHANGELOG.md">github/codeql-action's changelog</a>.</em></p> <blockquote> <h1>CodeQL Action Changelog</h1> <p>See the <a href="https://github.com/github/codeql-action/releases">releases page</a> for the relevant changes to the CodeQL CLI and language packs.</p> <p>Note that the only difference between <code>v2</code> and <code>v3</code> of the CodeQL Action is the node version they support, with <code>v3</code> running on node 20 while we continue to release <code>v2</code> to support running on node 16. For example <code>3.22.11</code> was the first <code>v3</code> release and is functionally identical to <code>2.22.11</code>. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.</p> <h2>[UNRELEASED]</h2> <p>No user facing changes.</p> <h2>3.23.1 - 17 Jan 2024</h2> <ul> <li>Update default CodeQL bundle version to 2.16.0. <a href="https://redirect.github.com/github/codeql-action/pull/2073">#2073</a></li> <li>Change the retention period for uploaded debug artifacts to 7 days. Previously, this was whatever the repository default was. <a href="https://redirect.github.com/github/codeql-action/pull/2079">#2079</a></li> </ul> <h2>3.23.0 - 08 Jan 2024</h2> <ul> <li>We are rolling out a feature in January 2024 that will disable Python dependency installation by default for all users. This improves the speed of analysis while having only a very minor impact on results. You can override this behavior by setting <code>CODEQL_ACTION_DISABLE_PYTHON_DEPENDENCY_INSTALLATION=false</code> in your workflow, however we plan to remove this ability in future versions of the CodeQL Action. <a href="https://redirect.github.com/github/codeql-action/pull/2031">#2031</a></li> <li>The CodeQL Action now requires CodeQL version 2.11.6 or later. For more information, see <a href="https://github.com/github/codeql-action/blob/main/#2227---16-nov-2023">the corresponding changelog entry for CodeQL Action version 2.22.7</a>. <a href="https://redirect.github.com/github/codeql-action/pull/2009">#2009</a></li> </ul> <h2>3.22.12 - 22 Dec 2023</h2> <ul> <li>Update default CodeQL bundle version to 2.15.5. <a href="https://redirect.github.com/github/codeql-action/pull/2047">#2047</a></li> </ul> <h2>3.22.11 - 13 Dec 2023</h2> <ul> <li>[v3+ only] The CodeQL Action now runs on Node.js v20. <a href="https://redirect.github.com/github/codeql-action/pull/2006">#2006</a></li> </ul> <h2>2.22.10 - 12 Dec 2023</h2> <ul> <li>Update default CodeQL bundle version to 2.15.4. <a href="https://redirect.github.com/github/codeql-action/pull/2016">#2016</a></li> </ul> <h2>2.22.9 - 07 Dec 2023</h2> <p>No user facing changes.</p> <h2>2.22.8 - 23 Nov 2023</h2> <ul> <li>Update default CodeQL bundle version to 2.15.3. <a href="https://redirect.github.com/github/codeql-action/pull/2001">#2001</a></li> </ul> <h2>2.22.7 - 16 Nov 2023</h2> <ul> <li>Add a deprecation warning for customers using CodeQL version 2.11.5 and earlier. These versions of CodeQL were discontinued on 8 November 2023 alongside GitHub Enterprise Server 3.7, and will be unsupported by CodeQL Action v2.23.0 and later. <a href="https://redirect.github.com/github/codeql-action/pull/1993">#1993</a> <ul> <li>If you are using one of these versions, please update to CodeQL CLI version 2.11.6 or later. For instance, if you have specified a custom version of the CLI using the 'tools' input to the 'init' Action, you can remove this input to use the default version.</li> <li>Alternatively, if you want to continue using a version of the CodeQL CLI between 2.10.5 and 2.11.5, you can replace <code>github/codeql-action/*@v2</code> by <code>github/codeql-action/*@v2.22.7</code> in your code scanning workflow to ensure you continue using this version of the CodeQL Action.</li> </ul> </li> </ul> <h2>2.22.6 - 14 Nov 2023</h2> <ul> <li>Customers running Python analysis on macOS using version 2.14.6 or earlier of the CodeQL CLI should upgrade to CodeQL CLI version 2.15.0 or later. If you do not wish to upgrade the CodeQL CLI, ensure that you are using Python version 3.11 or earlier, as CodeQL version 2.14.6 and earlier do not support Python 3.12. You can achieve this by adding a <a href="https://github.com/actions/setup-python"><code>setup-python</code></a> step to your code scanning workflow before the step that invokes <code>github/codeql-action/init</code>.</li> <li>Update default CodeQL bundle version to 2.15.2. <a href="https://redirect.github.com/github/codeql-action/pull/1978">#1978</a></li> </ul> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
|||
| a5b787505d |
[google_maps_flutter] Clean up iOS example project (#5925)
Follows up on https://github.com/flutter/packages/pull/5915 to remove the example-app-level workaround for the lack of arm64 slice, since the `flutter` build process will handle it automatically with current versions (now that the plugin-level workaround has been restored). Also fixes another problem I noticed while removing those, which is that when I federated this plugin I never removed the RunnerTests and RunnerUITests targets from this project, even though all of the files had moved, leaving missing file references and targets that would not build. This hadn't been noticed because our tooling doesn't even try to run native tests on plugins that indicate that their implementation is in a different package (and we rarely manually open the native projects for the app-facing package). |
|||
| 8ab9b253b6 |
[ci] Add flags to formatter command to decide which formatters to run (#5905)
Get ready for a world where `swift-format` is available on the `PATH` https://flutter-review.googlesource.com/c/recipes/+/54020 1. Add `format --clang-format --java --kotlin --swift --dart` flags to decide whether to run specific formatters, as opposed to using the `path`. Keep `swift-format` optional but default the others to run. This matches the current behavior on Linux. 2. Add `*-path` variants of each. This will allow us to run `format --swift --no-clang-format --no-java --no-kotlin --no-dart` on the macOS bot so it doesn't duplicate same `format` call run on Linux. Part of https://github.com/flutter/flutter/issues/41129 |
|||
| ef8ccdb471 |
Update tests to Xcode 15 and iOS 17 simulator (#5914)
Packages part of https://github.com/flutter/flutter/issues/132237. |
|||
| 2cc053334f |
Roll Flutter from def6af0b8e6e to f77f82435a97 (25 revisions) (#5924)
|
|||
| 83c2c4da97 |
[google_maps_flutter] Restore the arm64 workaround (#5915)
Restores the workaround to exclude arm64 when building for simulator, which is still necessary for apps that support back to iOS 12. Also removes all the example-app-level workarounds that manually excluded arm64 simulator, which were masking the failure in the first place, so that we don't accidentally break this again. The exception is the exclusions for the unit test targets, which need them in order to match the Flutter-tool-generated exclusion to the Runner, otherwise the unit tests can't build. See https://github.com/flutter/flutter/issues/94491google_maps_flutter_ios-v2.4.1 |
|||
| f2c1be0a70 |
[pigeon] Separates message call code generation into separate methods in the KotlinGenerator (#5891)
Separates message call code generation into separate methods in the KotlinGenerator for https://github.com/flutter/flutter/issues/134777. The ProxyApi generator uses similar code to the HostApi and FlutterApi, so this makes the code reusable. From suggestion: https://github.com/flutter/packages/pull/5544#discussion_r1445298086pigeon-v16.0.3 |
|||
| 669fd25723 |
[webview_flutter_wkebview] Verify JavaScriptChannels have a unique name (#5904)
Fixes https://github.com/flutter/flutter/issues/141242 According to [WKUserContentController.addScriptMessageHandler](https://developer.apple.com/documentation/webkit/wkusercontentcontroller/1537172-addscriptmessagehandler?language=objc), a handler must have a unique name. In https://github.com/flutter/flutter/issues/141242, this led to a crash. This PR prevents the app crash and throws an error from Dart when the method is called.webview_flutter_wkwebview-v3.10.3 |
|||
| a63122cb10 |
[pigeon] Separates message call code generation into separate methods in the DartGenerator (#5859)
Separates message call code generation into separate methods in the `DartGenerator` for https://github.com/flutter/flutter/issues/134777. The `ProxyApi` generator uses similar code to the `HostApi` and `FlutterApi`, so this makes the code reusable. Separated from https://github.com/flutter/packages/pull/5544 From suggestion: https://github.com/flutter/packages/pull/5544#discussion_r1445298086pigeon-v16.0.2 |
|||
| 807c2fcf43 |
Roll Flutter from 8e94423e6a92 to def6af0b8e6e (23 revisions) (#5911)
|
|||
| 1a2b780c91 |
Reverts "[ci] Run check_podspecs on arm Mac bots" (#5909)
Reverts flutter/packages#5885 Initiated by: jmagman This change reverts the following previous change: Original Description: Fixes https://github.com/flutter/flutter/issues/141493 |
|||
| 4c5375dbf5 |
[various] Update minimum iOS versions to 12.0 (#5902)
This makes the following mass changes: - Builds all examples with current stable (3.16.7), to pick up the auto-migration of projects to a minimum of iOS 12. - In some cases this picks up other boilerplate Xcode project migrations that had never been checked in to those projects. - Updates all iOS plugin implementations to indicate that they require iOS 12.0 or later. - Updates all the READMEs of the app-facing versions of those plugins to indicate that iOS 11 will no longer receive implementation updates. The only code changes are: - the removal of some `@available` checks in `in_app_purchase_storekit` that had become no-ops with the support change - the removal of a `!` in `camera_avfoundation` Dart code, which is no longer necessary due to changes in nullable field promotion in newer versions of Dart. These changes are version-exempt [per repo policy](https://github.com/flutter/flutter/wiki/Contributing-to-Plugins-and-Packages#version-and-changelog-updates), so the changelog changes all use NEXT. |
|||
| 855e283fa8 |
[ci] Run check_podspecs on arm Mac bots (#5885)
Fixes https://github.com/flutter/flutter/issues/141493 |
|||
| 82158e87d5 |
[pigeon] Fix pigeon test generation missing wrapResponse method. (#5903)
Pigeon was not generating the wrapResponse method, and therefore failing compilation of the generated tests. Fixes: https://github.com/flutter/flutter/issues/141499pigeon-v16.0.1 |
|||
| bf0752a471 |
Roll Flutter from 1a2c3151fef2 to 8e94423e6a92 (2 revisions) (#5897)
|
|||
| 83b5a67c36 |
Bump actions/upload-artifact from 3.1.3 to 4.1.0 (#5896)
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 3.1.3 to 4.1.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/upload-artifact/releases">actions/upload-artifact's releases</a>.</em></p> <blockquote> <h2>v4.1.0</h2> <h2>What's Changed</h2> <ul> <li>Add migrations docs by <a href="https://github.com/robherley"><code>@ârobherley</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/482">actions/upload-artifact#482</a></li> <li>Update README.md by <a href="https://github.com/samuelwine"><code>@âsamuelwine</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/492">actions/upload-artifact#492</a></li> <li>Support artifact-url output by <a href="https://github.com/konradpabjan"><code>@âkonradpabjan</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/496">actions/upload-artifact#496</a></li> <li>Update readme to reflect new 500 artifact per job limit by <a href="https://github.com/robherley"><code>@ârobherley</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/497">actions/upload-artifact#497</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/samuelwine"><code>@âsamuelwine</code></a> made their first contribution in <a href="https://redirect.github.com/actions/upload-artifact/pull/492">actions/upload-artifact#492</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/upload-artifact/compare/v4...v4.1.0">https://github.com/actions/upload-artifact/compare/v4...v4.1.0</a></p> <h2>v4.0.0</h2> <h2>What's Changed</h2> <p>The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.</p> <p>â¹ï¸ However, this is a major update that includes breaking changes. Artifacts created with versions v3 and below are not compatible with the v4 actions. Uploads and downloads <em>must</em> use the same major actions versions. There are also key differences from previous versions that may require updates to your workflows.</p> <p>For more information, please see:</p> <ol> <li>The <a href="https://github.blog/changelog/2023-12-14-github-actions-artifacts-v4-is-now-generally-available/">changelog</a> post.</li> <li>The <a href="https://github.com/actions/upload-artifact/blob/main/README.md">README</a>.</li> <li>The <a href="https://github.com/actions/upload-artifact/blob/main/docs/MIGRATION.md">migration documentation</a>.</li> <li>As well as the underlying npm package, <a href="https://github.com/actions/toolkit/tree/main/packages/artifact"><code>@âactions/artifact</code></a> documentation.</li> </ol> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/vmjoseph"><code>@âvmjoseph</code></a> made their first contribution in <a href="https://redirect.github.com/actions/upload-artifact/pull/464">actions/upload-artifact#464</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/upload-artifact/compare/v3...v4.0.0">https://github.com/actions/upload-artifact/compare/v3...v4.0.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
|||
| 7dd0fcbcfa |
Bump release to use 3.16.6 (#5886)
google_maps_flutter_ios now requires 3.16.6, so we need to bump the release script so that it can be published by CI. Fixes the tree. |
|||
| dd7b3a35fb |
[rfw] Add support for tracking source locations of BlobNodes. (#5876)
Fixes https://github.com/flutter/flutter/issues/141070.rfw-v1.0.17 |
|||
| d21f3b861e |
Roll Flutter from 7dc856ab8423 to 1a2c3151fef2 (23 revisions) (#5895)
|
|||
| dea6c7306c |
[webview_flutter_android] Add test that onReceivedHttpAuthRequest is cancelled by default (#5723)
Added test in response to feedback from https://github.com/flutter/packages/pull/5454#pullrequestreview-1780163572 Also regenerates mock files. |
|||
| 6abb0dd275 |
Roll Flutter (stable) from 46787ee49c1f to ef1af02aead6 (1 revision) (#5887)
|
|||
| 14b94ff834 |
[google_maps_flutter] Drop iOS 11 support (#5873)
Now that the latest Flutter stable requires iOS 12, and will auto-adjust projects, we can drop iOS 11 support in this plugin without breaking users. Having a minimum of iOS 12 means that Cocoapods should not resolve to anything older than Google Maps 6.x, which is the version that add arm64 simulator support, so the workaround to explicitly not build that can be removed. This means `google_maps_flutter` will no longer force projects into the buggier Rosetta iOS simulator path. This folds the iOS 11 and iOS 12 examples together, since (per `examples/README.md`) the iOS 11 version is the one containing most of the tests. To minimize the potential of losing tests due to mistakes, this was done by deleting the iOS *12* example, renaming the iOS 11 example, and then updating it to a minimum of 12. Fixes https://github.com/flutter/flutter/issues/94491google_maps_flutter-v2.5.3 google_maps_flutter_ios-v2.4.0 |
|||
| c9d8fb690b |
Roll Flutter from 9f2e681e7be6 to 7dc856ab8423 (15 revisions) (#5882)
|
|||
| d74d687dc0 |
[ci] Check repo-level package metadata (#5811)
Adds a new tool command (and runs it in CI) to check that each package: - is listed correctly in the repo-level README.md table - has a CODEOWNERS entry In the future we could add other things (e.g., auto-label), but these were the main things we've had issues with recently. Updates README.md and CODEOWNERS to fix failures it found: - Adds a couple of missing CODEOWNERS - Expands the web implementation CODEOWNERS to individual packages so that we don't have to special-case handling in the tool - Fixes some minor mistakes in README.md - URL-encodes all `:`s in the README.md links (which is why ever line shows as changed); it worked without that in practice, but it should really be encoded, and having it consistently encoded made things easier for the tooling. |
|||
| c5349bc9a5 |
[various] Add iOS privacy manifests (#5846)
Adds privacy manifests to all iOS plugins. While we only *need* to do the plugins listed [here](https://developer.apple.com/support/third-party-SDK-requirements/) for now, the wording of the page: > The following are commonly used SDKs in apps on the App Store suggests that the list of things for which this is required is just an arbitrary cutoff rather than a conceptual distinction, so it seems safest to just assume the list will grow over time and do all of them. To ensure that, this includes new repo tooling to check that a manifest is specified in the podspec. The large caveat is that we do not currently know if this actually works. This is the method of inclusion that seems to be [the consensus among people using Cocoapods](https://github.com/CocoaPods/CocoaPods/issues/10325), as bundling it directly as a `resource` causes problems for clients who do not use `use_frameworks`. (In theory it seems like a manifest would not actually be *required* in that case since there is no framework, but it has the potential to actually stomp top-level resources.) Hopefully the automated analysis that Apple will eventually roll out will tolerate the file being bundled in a resource bundle in the framework rather than a top-level manifest file. If not, however, it's not clear how Cocoapods can be supported, so we can adopt this common approach for now under the assumption that eventually tooling will adapt to the reality of the ecosystem, and revisit the exact bundling later if necessary. Only `shared_preferences` has a non-empty manifest, as it is our only plugin that uses a required reason API, and none of our plugins themselves collect private data. Ideally for that plugin we would instead use `C56D.1`, which is for wrappers, but as currently written we can't use it since it's exclusively a wrapper. If that changes in the future based on our pending request, we can revisit. For now, however, this reason should suffice since we don't currently allow reading from other app groups. Fixes https://github.com/flutter/flutter/issues/131495 Fixes https://github.com/flutter/flutter/issues/139756 Fixes https://github.com/flutter/flutter/issues/139757 Fixes https://github.com/flutter/flutter/issues/139758 Fixes https://github.com/flutter/flutter/issues/139759 Fixes https://github.com/flutter/flutter/issues/139760 See also https://github.com/flutter/flutter/issues/139761local_auth_ios-v1.1.6 pointer_interceptor_ios-v0.10.0+2 camera_avfoundation-v0.9.13+10 google_sign_in_ios-v5.7.3 shared_preferences_foundation-v2.3.5 google_maps_flutter_ios-v2.3.6 video_player_avfoundation-v2.5.6 image_picker_ios-v0.8.9+1 url_launcher_ios-v6.2.4 quick_actions_ios-v1.0.10 webview_flutter_wkwebview-v3.10.2 file_selector_ios-v0.5.1+8 ios_platform_images-v0.2.3+2 in_app_purchase_storekit-v0.3.8+1 path_provider_foundation-v2.3.2 |
|||
| b61735b00e |
[video_player] Skip flaky tests in certain circumstances on Android (#5872)
Temporary workaround for https://github.com/flutter/flutter/issues/141145 This doesn't fully skip the test because this problem doesn't happen in CI device tests or locally, so rather than totally lose coverage this detects the very specific markers of this flake and skips only when that happens. This should allow the tree to stop being so red with the minimal coverage loss while we investigate this further. Part of https://github.com/flutter/flutter/issues/141145 |
|||
| 5fd5fb9998 |
Roll Flutter (stable) from 78666c8dc57e to 46787ee49c1f (5 revisions) (#5870)
|
|||
| d2321c4e5f |
Roll Flutter from b840a60d7d3f to 9f2e681e7be6 (24 revisions) (#5871)
|
|||
| 0744fe6fdb |
[quick_actions_android] Close system dialogs for integration test (#5853)
Fixes https://github.com/flutter/flutter/issues/141136 Temporary fix for https://github.com/flutter/flutter/issues/140987 |
|||
| 15000e7209 |
[file_selector]: Bump androidx.annotation:annotation from 1.7.0 to 1.7.1 in /packages/file_selector/file_selector_android/android (#5712)
Bumps androidx.annotation:annotation from 1.7.0 to 1.7.1. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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`. --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details>file_selector_android-v0.5.0+7 |
|||
| 8255fbed74 |
[in_app_pur]: Bump androidx.annotation:annotation from 1.7.0 to 1.7.1 in /packages/in_app_purchase/in_app_purchase_android/android (#5713)
Bumps androidx.annotation:annotation from 1.7.0 to 1.7.1. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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`. --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details>in_app_purchase_android-v0.3.0+17 |
|||
| 93e4bc0781 |
[url_launcher]: Bump androidx.annotation:annotation from 1.7.0 to 1.7.1 in /packages/url_launcher/url_launcher_android/android (#5708)
Bumps androidx.annotation:annotation from 1.7.0 to 1.7.1. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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`. --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> |
|||
| bb0cac8fac |
[image_picker]: Bump androidx.annotation:annotation from 1.7.0 to 1.7.1 in /packages/image_picker/image_picker_android/android (#5703)
Bumps androidx.annotation:annotation from 1.7.0 to 1.7.1. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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`. --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details>image_picker_android-v0.8.9+3 |
|||
| 347929fc60 |
Roll Flutter from 126302dfb44c to b840a60d7d3f (29 revisions) (#5855)
|
|||
| 378e700068 |
Roll Flutter from c6ddb73f971e to 126302dfb44c (32 revisions) (#5852)
Roll Flutter from c6ddb73f971e to 126302dfb44c (32 revisions)
|
|||
| 70cc569a54 |
Bump github/codeql-action from 3.22.12 to 3.23.0 (#5849)
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.22.12 to 3.23.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/github/codeql-action/blob/main/CHANGELOG.md">github/codeql-action's changelog</a>.</em></p> <blockquote> <h1>CodeQL Action Changelog</h1> <p>See the <a href="https://github.com/github/codeql-action/releases">releases page</a> for the relevant changes to the CodeQL CLI and language packs.</p> <p>Note that the only difference between <code>v2</code> and <code>v3</code> of the CodeQL Action is the node version they support, with <code>v3</code> running on node 20 while we continue to release <code>v2</code> to support running on node 16. For example <code>3.22.11</code> was the first <code>v3</code> release and is functionally identical to <code>2.22.11</code>. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.</p> <h2>[UNRELEASED]</h2> <p>No user facing changes.</p> <h2>3.23.0 - 08 Jan 2024</h2> <ul> <li>We are rolling out a feature in January 2024 that will disable Python dependency installation by default for all users. This improves the speed of analysis while having only a very minor impact on results. You can override this behavior by setting <code>CODEQL_ACTION_DISABLE_PYTHON_DEPENDENCY_INSTALLATION=false</code> in your workflow, however we plan to remove this ability in future versions of the CodeQL Action. <a href="https://redirect.github.com/github/codeql-action/pull/2031">#2031</a></li> <li>The CodeQL Action now requires CodeQL version 2.11.6 or later. For more information, see <a href="https://github.com/github/codeql-action/blob/main/#2227---16-nov-2023">the corresponding changelog entry for CodeQL Action version 2.22.7</a>. <a href="https://redirect.github.com/github/codeql-action/pull/2009">#2009</a></li> </ul> <h2>3.22.12 - 22 Dec 2023</h2> <ul> <li>Update default CodeQL bundle version to 2.15.5. <a href="https://redirect.github.com/github/codeql-action/pull/2047">#2047</a></li> </ul> <h2>3.22.11 - 13 Dec 2023</h2> <ul> <li>[v3+ only] The CodeQL Action now runs on Node.js v20. <a href="https://redirect.github.com/github/codeql-action/pull/2006">#2006</a></li> </ul> <h2>2.22.10 - 12 Dec 2023</h2> <ul> <li>Update default CodeQL bundle version to 2.15.4. <a href="https://redirect.github.com/github/codeql-action/pull/2016">#2016</a></li> </ul> <h2>2.22.9 - 07 Dec 2023</h2> <p>No user facing changes.</p> <h2>2.22.8 - 23 Nov 2023</h2> <ul> <li>Update default CodeQL bundle version to 2.15.3. <a href="https://redirect.github.com/github/codeql-action/pull/2001">#2001</a></li> </ul> <h2>2.22.7 - 16 Nov 2023</h2> <ul> <li>Add a deprecation warning for customers using CodeQL version 2.11.5 and earlier. These versions of CodeQL were discontinued on 8 November 2023 alongside GitHub Enterprise Server 3.7, and will be unsupported by CodeQL Action v2.23.0 and later. <a href="https://redirect.github.com/github/codeql-action/pull/1993">#1993</a> <ul> <li>If you are using one of these versions, please update to CodeQL CLI version 2.11.6 or later. For instance, if you have specified a custom version of the CLI using the 'tools' input to the 'init' Action, you can remove this input to use the default version.</li> <li>Alternatively, if you want to continue using a version of the CodeQL CLI between 2.10.5 and 2.11.5, you can replace <code>github/codeql-action/*@v2</code> by <code>github/codeql-action/*@v2.22.7</code> in your code scanning workflow to ensure you continue using this version of the CodeQL Action.</li> </ul> </li> </ul> <h2>2.22.6 - 14 Nov 2023</h2> <ul> <li>Customers running Python analysis on macOS using version 2.14.6 or earlier of the CodeQL CLI should upgrade to CodeQL CLI version 2.15.0 or later. If you do not wish to upgrade the CodeQL CLI, ensure that you are using Python version 3.11 or earlier, as CodeQL version 2.14.6 and earlier do not support Python 3.12. You can achieve this by adding a <a href="https://github.com/actions/setup-python"><code>setup-python</code></a> step to your code scanning workflow before the step that invokes <code>github/codeql-action/init</code>.</li> <li>Update default CodeQL bundle version to 2.15.2. <a href="https://redirect.github.com/github/codeql-action/pull/1978">#1978</a></li> </ul> <h2>2.22.5 - 27 Oct 2023</h2> <p>No user facing changes.</p> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
|||
| 09205ca19b |
Re-land: Enable prefer_mixin and bump plugin_platform_interface to 2.1.7 (#5841)
This reverts commit
path_provider-v2.1.2
webview_flutter_platform_interface-v2.9.1
camera_platform_interface-v2.7.2
video_player_platform_interface-v6.2.2
file_selector_platform_interface-v2.6.2
camera-v0.10.5+9
webview_flutter-v4.4.4
local_auth-v2.1.8
url_launcher_ios-v6.2.3
google_sign_in_platform_interface-v2.4.5
in_app_purchase_platform_interface-v1.3.7
url_launcher_android-v6.2.2
google_maps_flutter_android-v2.6.2
quick_actions_ios-v1.0.9
image_picker-v1.0.7
quick_actions_platform_interface-v1.0.6
in_app_purchase-v3.1.13
url_launcher-v6.2.3
url_launcher_platform_interface-v2.3.1
quick_actions-v1.0.7
quick_actions_android-v1.0.10
google_maps_flutter-v2.5.2
pointer_interceptor_web-v0.10.1+1
file_selector-v1.0.2
google_maps_flutter_platform_interface-v2.4.3
pointer_interceptor_platform_interface-v0.10.0+1
google_maps_flutter_ios-v2.3.5
path_provider_platform_interface-v2.1.2
file_selector_android-v0.5.0+6
pointer_interceptor_ios-v0.10.0+1
image_picker_platform_interface-v2.9.3
local_auth_platform_interface-v1.0.10
shared_preferences_platform_interface-v2.3.2
|
