文件最后提交记录最后更新时间
[ci] Move tool_runner.sh (#6038) script/tool_runner.sh has only been intended for CI usage for quite a while, but it still lives in a prominent non-CI location which has been a source of confusion for developers (e.g., people looking at how CI is running things, and reasonably assuming that since the script isn't in a CI-specific location, it's for general use). While running it for simple cases works, it conflicts with any package selection, which is common thing to want to control when running locally. This makes the following changes: - Move the script into the .ci directory - Adds explicit comments that it's not designed for local use, with a pointer to the corresponding local command - Removes a stale reference to external-to-the-repo use of tool_runner.sh, as that usage no longer exists - Also consolidates and updates the links to the external scripts - Updates a couple of CONTRIBUTING.md comments that still said to run tool_runner.sh - Opportunistically cleans up some tooling references to .cirrus.yml, found while cleaning up comments in tool_runner.sh and checking for other references.2 年前
[ci] Move tool_runner.sh (#6038) script/tool_runner.sh has only been intended for CI usage for quite a while, but it still lives in a prominent non-CI location which has been a source of confusion for developers (e.g., people looking at how CI is running things, and reasonably assuming that since the script isn't in a CI-specific location, it's for general use). While running it for simple cases works, it conflicts with any package selection, which is common thing to want to control when running locally. This makes the following changes: - Move the script into the .ci directory - Adds explicit comments that it's not designed for local use, with a pointer to the corresponding local command - Removes a stale reference to external-to-the-repo use of tool_runner.sh, as that usage no longer exists - Also consolidates and updates the links to the external scripts - Updates a couple of CONTRIBUTING.md comments that still said to run tool_runner.sh - Opportunistically cleans up some tooling references to .cirrus.yml, found while cleaning up comments in tool_runner.sh and checking for other references.2 年前
Update Flutter wiki links (#6789) Updates all links to the Flutter wiki to point to their new location in the flutter/flutter repository. (The sole exception is a link to a doc that doesn't have a final home yet, and is linked from legacy code anyway so doesn't really need to be updated.) While touching the PR template, makes a few minor improvements: - Removes the breaking change discussion that doesn't apply to this repository, as breaking changes are handled totally differently for packages (and is covered by the link to docs about Dart versioning). - Adds text and a link to reflect the fact that some PRs can be changelog-exempt.1 年前
[all_packages] Bump compileSdk version to 35 (#9168) Bumps all_packages app to build with compileSdk version 35. Then, - Updates the Gradle and AGP versions to support this new Android SDK version - Refactors the legacy all_packages CI build target such that the regular all_packages CI build targets (master, stable) will build both the modern all_packages app and the legacy version with the same JDK 17 version, since the legacy version now also requires it (example successful builds: [master](https://ci.chromium.org/ui/p/flutter/builders/try/Linux_android%20android_build_all_packages%20master/17102/overview), [stable](https://ci.chromium.org/ui/p/flutter/builders/try/Linux_android%20android_build_all_packages%20stable/17086/overview)) - Updates legacy all_packages app README.md to more accurately describe how the app was transformed since its creation Prompted by https://github.com/flutter/packages/pull/8414. ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.11 个月前
[ci] Move tool_runner.sh (#6038) script/tool_runner.sh has only been intended for CI usage for quite a while, but it still lives in a prominent non-CI location which has been a source of confusion for developers (e.g., people looking at how CI is running things, and reasonably assuming that since the script isn't in a CI-specific location, it's for general use). While running it for simple cases works, it conflicts with any package selection, which is common thing to want to control when running locally. This makes the following changes: - Move the script into the .ci directory - Adds explicit comments that it's not designed for local use, with a pointer to the corresponding local command - Removes a stale reference to external-to-the-repo use of tool_runner.sh, as that usage no longer exists - Also consolidates and updates the links to the external scripts - Updates a couple of CONTRIBUTING.md comments that still said to run tool_runner.sh - Opportunistically cleans up some tooling references to .cirrus.yml, found while cleaning up comments in tool_runner.sh and checking for other references.2 年前
[ci] Move tool_runner.sh (#6038) script/tool_runner.sh has only been intended for CI usage for quite a while, but it still lives in a prominent non-CI location which has been a source of confusion for developers (e.g., people looking at how CI is running things, and reasonably assuming that since the script isn't in a CI-specific location, it's for general use). While running it for simple cases works, it conflicts with any package selection, which is common thing to want to control when running locally. This makes the following changes: - Move the script into the .ci directory - Adds explicit comments that it's not designed for local use, with a pointer to the corresponding local command - Removes a stale reference to external-to-the-repo use of tool_runner.sh, as that usage no longer exists - Also consolidates and updates the links to the external scripts - Updates a couple of CONTRIBUTING.md comments that still said to run tool_runner.sh - Opportunistically cleans up some tooling references to .cirrus.yml, found while cleaning up comments in tool_runner.sh and checking for other references.2 年前
[Android][webview_flutter] Run integration tests on emulators running Android 34 (#6499) Changes webview_flutter , webview_flutter_android tests to run on emulators running SDK 34 for Android. I also 1. Changed all unawaited calls in non-legacy tests to await. I believe several of the setup steps need to be completed before running checks based on testing, so this should leave the tests safer overall. 2. Changing the integration test directory structures look like what is described in [the integration_test packages instructions](https://github.com/flutter/flutter/blob/master/packages/integration_test/README.md#package-structure). Without changing the package to this structure, CI seemed to run the tests in parallel. I am still trying to figure out why this is but no longer want to block this PR. Also removes shards for testing packages against Android 33 since no packages are running on emulators running Android 33 anymore. Fixes https://github.com/flutter/flutter/issues/140001. Fixes https://github.com/flutter/flutter/issues/137083.2 年前
[ci] Move tool_runner.sh (#6038) script/tool_runner.sh has only been intended for CI usage for quite a while, but it still lives in a prominent non-CI location which has been a source of confusion for developers (e.g., people looking at how CI is running things, and reasonably assuming that since the script isn't in a CI-specific location, it's for general use). While running it for simple cases works, it conflicts with any package selection, which is common thing to want to control when running locally. This makes the following changes: - Move the script into the .ci directory - Adds explicit comments that it's not designed for local use, with a pointer to the corresponding local command - Removes a stale reference to external-to-the-repo use of tool_runner.sh, as that usage no longer exists - Also consolidates and updates the links to the external scripts - Updates a couple of CONTRIBUTING.md comments that still said to run tool_runner.sh - Opportunistically cleans up some tooling references to .cirrus.yml, found while cleaning up comments in tool_runner.sh and checking for other references.2 年前
[google_sign_in_ios] Upgrade GoogleSignIn iOS SDK to 7.1 (#6404) 1. Update GoogleSignIn iOS SDK dependency to [7.1](https://github.com/google/GoogleSignIn-iOS/releases/tag/7.1.0), which supports privacy manifests. 1. Update "fetch deps step" to run pod repo update every time to avoid missing spec failure. Also added a fetch deps step to the all_packages builds, since those could also use a pod repo update but I didn't want to add more logic to those bash scripts. ``` [!] CocoaPods could not find compatible versions for pod "GoogleSignIn": In Podfile: google_sign_in_ios (from Flutter/ephemeral/.symlinks/plugins/google_sign_in_ios/darwin) was resolved to 0.0.1, which depends on GoogleSignIn (~> 7.1) None of your spec sources contain a spec satisfying the dependency: GoogleSignIn (~> 7.1). ``` https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8752192509749702705/+/u/Run_package_tests/download_Dart_and_iOS_deps/stdout 3. Looks like the new versions of [GTMSessionFetcher](https://github.com/CocoaPods/Specs/blob/master/Specs/c/e/3/GTMSessionFetcher/3.3.2/GTMSessionFetcher.podspec.json) and [AppAuth](https://github.com/CocoaPods/Specs/blob/master/Specs/b/b/9/AppAuth/1.7.3/AppAuth.podspec.json) don't define modules, so there's an error building it statically: ``` [!] The following Swift pods cannot yet be integrated as static libraries: The Swift pod GTMAppAuth depends upon GTMSessionFetcher and AppAuth, which do not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies. ``` I filed https://github.com/google/gtm-session-fetcher/issues/384 and https://github.com/openid/AppAuth-iOS/issues/844. In the meantime, I updated the example apps to use_frameworks!, which would be on for Flutter Swift apps, but not Objective-C ones. We could add something to the tool to detect this case, and suggest use_frameworks! be added? 4. Even though google_sign_in_ios does not contain Swift files, for some reason, there is a "pod lib lint" warning complaining swift_version isn't set. This seems related to GTMAppAuth dependency constraint that went from an Objective-C-only to Swift pod. So I set swift_version since it's harmless. ``` - WARN | swift: The validator used Swift 4.0 by default because no Swift version was specified. To specify a Swift version during validation, add the swift_versions attribute in your podspec. Note that usage of a .swift-version file is now deprecated. ``` https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8752100979634945505/+/u/Run_package_tests/validate_iOS_and_macOS_podspecs/stdout ## Issues * Fixes https://github.com/flutter/flutter/issues/145777 * Fixes https://github.com/flutter/flutter/issues/145866 * See also https://github.com/flutter/flutter/issues/1371402 年前
Upgrade tests to use Xcode 16 and iOS 18 (#8968) Fixes https://github.com/flutter/flutter/issues/148956. ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.1 年前
[tooling] mark infra steps as infra steps in yaml files (#4473) - Add infra notation to infra tasks in packages repo https://github.com/flutter/flutter/issues/1305982 年前
[ci] Move tool_runner.sh (#6038) script/tool_runner.sh has only been intended for CI usage for quite a while, but it still lives in a prominent non-CI location which has been a source of confusion for developers (e.g., people looking at how CI is running things, and reasonably assuming that since the script isn't in a CI-specific location, it's for general use). While running it for simple cases works, it conflicts with any package selection, which is common thing to want to control when running locally. This makes the following changes: - Move the script into the .ci directory - Adds explicit comments that it's not designed for local use, with a pointer to the corresponding local command - Removes a stale reference to external-to-the-repo use of tool_runner.sh, as that usage no longer exists - Also consolidates and updates the links to the external scripts - Updates a couple of CONTRIBUTING.md comments that still said to run tool_runner.sh - Opportunistically cleans up some tooling references to .cirrus.yml, found while cleaning up comments in tool_runner.sh and checking for other references.2 年前
[ci] Move tool_runner.sh (#6038) script/tool_runner.sh has only been intended for CI usage for quite a while, but it still lives in a prominent non-CI location which has been a source of confusion for developers (e.g., people looking at how CI is running things, and reasonably assuming that since the script isn't in a CI-specific location, it's for general use). While running it for simple cases works, it conflicts with any package selection, which is common thing to want to control when running locally. This makes the following changes: - Move the script into the .ci directory - Adds explicit comments that it's not designed for local use, with a pointer to the corresponding local command - Removes a stale reference to external-to-the-repo use of tool_runner.sh, as that usage no longer exists - Also consolidates and updates the links to the external scripts - Updates a couple of CONTRIBUTING.md comments that still said to run tool_runner.sh - Opportunistically cleans up some tooling references to .cirrus.yml, found while cleaning up comments in tool_runner.sh and checking for other references.2 年前
[google_sign_in_ios] Upgrade GoogleSignIn iOS SDK to 7.1 (#6404) 1. Update GoogleSignIn iOS SDK dependency to [7.1](https://github.com/google/GoogleSignIn-iOS/releases/tag/7.1.0), which supports privacy manifests. 1. Update "fetch deps step" to run pod repo update every time to avoid missing spec failure. Also added a fetch deps step to the all_packages builds, since those could also use a pod repo update but I didn't want to add more logic to those bash scripts. ``` [!] CocoaPods could not find compatible versions for pod "GoogleSignIn": In Podfile: google_sign_in_ios (from Flutter/ephemeral/.symlinks/plugins/google_sign_in_ios/darwin) was resolved to 0.0.1, which depends on GoogleSignIn (~> 7.1) None of your spec sources contain a spec satisfying the dependency: GoogleSignIn (~> 7.1). ``` https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8752192509749702705/+/u/Run_package_tests/download_Dart_and_iOS_deps/stdout 3. Looks like the new versions of [GTMSessionFetcher](https://github.com/CocoaPods/Specs/blob/master/Specs/c/e/3/GTMSessionFetcher/3.3.2/GTMSessionFetcher.podspec.json) and [AppAuth](https://github.com/CocoaPods/Specs/blob/master/Specs/b/b/9/AppAuth/1.7.3/AppAuth.podspec.json) don't define modules, so there's an error building it statically: ``` [!] The following Swift pods cannot yet be integrated as static libraries: The Swift pod GTMAppAuth depends upon GTMSessionFetcher and AppAuth, which do not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies. ``` I filed https://github.com/google/gtm-session-fetcher/issues/384 and https://github.com/openid/AppAuth-iOS/issues/844. In the meantime, I updated the example apps to use_frameworks!, which would be on for Flutter Swift apps, but not Objective-C ones. We could add something to the tool to detect this case, and suggest use_frameworks! be added? 4. Even though google_sign_in_ios does not contain Swift files, for some reason, there is a "pod lib lint" warning complaining swift_version isn't set. This seems related to GTMAppAuth dependency constraint that went from an Objective-C-only to Swift pod. So I set swift_version since it's harmless. ``` - WARN | swift: The validator used Swift 4.0 by default because no Swift version was specified. To specify a Swift version during validation, add the swift_versions attribute in your podspec. Note that usage of a .swift-version file is now deprecated. ``` https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8752100979634945505/+/u/Run_package_tests/validate_iOS_and_macOS_podspecs/stdout ## Issues * Fixes https://github.com/flutter/flutter/issues/145777 * Fixes https://github.com/flutter/flutter/issues/145866 * See also https://github.com/flutter/flutter/issues/1371402 年前
[tooling] mark infra steps as infra steps in yaml files (#4473) - Add infra notation to infra tasks in packages repo https://github.com/flutter/flutter/issues/1305982 年前
Reverts "[ci] Check macOS 15 for Xcode analyzer warnings (#9427)" (#9509) Reverts: flutter/packages#9427 Initiated by: ash2moon Reason for reverting: Looks like this is causing MacOS analyze tasks to fail: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_arm64%20macos_platform_tests%20stable%20-%20packages/3087/overview https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8710976140284515969/+/u/Run_package_tests/xcode_analyze_deprecation/stdout?format=raw Original PR Author: jmagman Reviewed By: {vashworth} This change reverts the following previous change: Xcode 16 is available in CI as of https://github.com/flutter/packages/pull/8968. Check all packages for macOS 15 deprecations. The last bump https://github.com/flutter/packages/pull/7544 Related https://github.com/flutter/plugins/pull/5778 and https://github.com/flutter/flutter/issues/102835 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.10 个月前
[ci] Move tool_runner.sh (#6038) script/tool_runner.sh has only been intended for CI usage for quite a while, but it still lives in a prominent non-CI location which has been a source of confusion for developers (e.g., people looking at how CI is running things, and reasonably assuming that since the script isn't in a CI-specific location, it's for general use). While running it for simple cases works, it conflicts with any package selection, which is common thing to want to control when running locally. This makes the following changes: - Move the script into the .ci directory - Adds explicit comments that it's not designed for local use, with a pointer to the corresponding local command - Removes a stale reference to external-to-the-repo use of tool_runner.sh, as that usage no longer exists - Also consolidates and updates the links to the external scripts - Updates a couple of CONTRIBUTING.md comments that still said to run tool_runner.sh - Opportunistically cleans up some tooling references to .cirrus.yml, found while cleaning up comments in tool_runner.sh and checking for other references.2 年前
Update repo for 3.32 stable (#9311) Does all of the steps from https://github.com/flutter/flutter/blob/master/docs/ecosystem/release/Updating-Packages-repo-for-a-stable-release.md for the 3.32 stable release (except the first one, as the stable roller has already landed).11 个月前
[tooling] mark infra steps as infra steps in yaml files (#4473) - Add infra notation to infra tasks in packages repo https://github.com/flutter/flutter/issues/1305982 年前
[ci] Add Wasm compilation to all_packages web app. (#6981) Adds a "--wasm" mode to create and build "all_packages" app to verify all our plugins compile with Wasm. Except not all do for now, so this also adds a "exclude_all_packages_app_wasm.yaml" file that allows us to remove the packages that aren't fully compatible yet. ## Issues * Fixes: https://github.com/flutter/flutter/issues/150748 * Related: https://github.com/flutter/flutter/issues/117022 * Related: https://github.com/flutter/flutter/issues/1486241 年前
[ci] Run web tests in wasm (unit + integration). (#8111) Adds CI configuration to run web integration tests (in the master channel) compiled to Wasm. It also removes the build-examples step from web integration tests, in some isolated testing: | platform tests shard | With build-examples | Without build-examples | |---|-----|-----| | 1 | 30m | 21m | | 2 | 13m | 11m | | 3 | 17m | 10m | ## Issues * Fixes https://github.com/flutter/flutter/issues/1516641 年前
[ci] Run web tests in wasm (unit + integration). (#8111) Adds CI configuration to run web integration tests (in the master channel) compiled to Wasm. It also removes the build-examples step from web integration tests, in some isolated testing: | platform tests shard | With build-examples | Without build-examples | |---|-----|-----| | 1 | 30m | 21m | | 2 | 13m | 11m | | 3 | 17m | 10m | ## Issues * Fixes https://github.com/flutter/flutter/issues/1516641 年前
[ci] Run web tests in wasm (unit + integration). (#8111) Adds CI configuration to run web integration tests (in the master channel) compiled to Wasm. It also removes the build-examples step from web integration tests, in some isolated testing: | platform tests shard | With build-examples | Without build-examples | |---|-----|-----| | 1 | 30m | 21m | | 2 | 13m | 11m | | 3 | 17m | 10m | ## Issues * Fixes https://github.com/flutter/flutter/issues/1516641 年前
[ci] Run web tests in wasm (unit + integration). (#8111) Adds CI configuration to run web integration tests (in the master channel) compiled to Wasm. It also removes the build-examples step from web integration tests, in some isolated testing: | platform tests shard | With build-examples | Without build-examples | |---|-----|-----| | 1 | 30m | 21m | | 2 | 13m | 11m | | 3 | 17m | 10m | ## Issues * Fixes https://github.com/flutter/flutter/issues/1516641 年前
[tooling] mark infra steps as infra steps in yaml files (#4473) - Add infra notation to infra tasks in packages repo https://github.com/flutter/flutter/issues/1305982 年前
[ci] Move tool_runner.sh (#6038) script/tool_runner.sh has only been intended for CI usage for quite a while, but it still lives in a prominent non-CI location which has been a source of confusion for developers (e.g., people looking at how CI is running things, and reasonably assuming that since the script isn't in a CI-specific location, it's for general use). While running it for simple cases works, it conflicts with any package selection, which is common thing to want to control when running locally. This makes the following changes: - Move the script into the .ci directory - Adds explicit comments that it's not designed for local use, with a pointer to the corresponding local command - Removes a stale reference to external-to-the-repo use of tool_runner.sh, as that usage no longer exists - Also consolidates and updates the links to the external scripts - Updates a couple of CONTRIBUTING.md comments that still said to run tool_runner.sh - Opportunistically cleans up some tooling references to .cirrus.yml, found while cleaning up comments in tool_runner.sh and checking for other references.2 年前
[tooling] mark infra steps as infra steps in yaml files (#4473) - Add infra notation to infra tasks in packages repo https://github.com/flutter/flutter/issues/1305982 年前
[tooling] mark infra steps as infra steps in yaml files (#4473) - Add infra notation to infra tasks in packages repo https://github.com/flutter/flutter/issues/1305982 年前