Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: flutter/packages
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 03352b5
Choose a base ref
...
head repository: flutter/packages
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 61bdbb4
Choose a head ref
  • 5 commits
  • 92 files changed
  • 3 contributors

Commits on Jun 4, 2026

  1. [ci] Renames the override post-release label for batch release (#11835) 

    The repo check ci will be run when creating release pr against release branch. In that case, we want to ignore the check to guard changes to changelog.md and pubspec.

The solution will be reusing the `override: post-release-*` label. I decide to also rename the label to `override: skip-batch-release-repo-check-*` since the original name is not appropriate in this use case.

## Pre-Review Checklist

**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

[^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.
    @chunhtai
    chunhtai authored Jun 4, 2026
    Configuration menu
    Copy the full SHA
    c584f33 View commit details
    Browse the repository at this point in the history

  2. [webview] Add new method for cross plugin webview access (#11714) 

    A new way of supporting cross plugin communication is coming in Flutter 3.44 which allows for access to plugin published values through the `FlutterPluginBinding` on Android and the `FlutterPluginRegistry` on iOS. Update native WebView access to support these new methods and deprecate the old methods.

refs: flutter/flutter#121527 flutter/flutter#182753

## Pre-Review Checklist
    @fuzzybinary
    fuzzybinary authored Jun 4, 2026
    Configuration menu
    Copy the full SHA
    6a2d543 View commit details
    Browse the repository at this point in the history

  3. [path_provider] Create temp dir in tests if needed (#11841) 

    The integration test step that validates that a file can be created in the returned directory assumes that the directory already exists, which isn't guaranteed to be true for getTemporaryDirectory, and this is now failing on macOS in CI. To avoid the failure, create the directory if necessary for the tests that run on macOS.

Hopefully fixes flutter/flutter#187563

## 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.
    @stuartmorgan-g
    stuartmorgan-g authored Jun 4, 2026
    Configuration menu
    Copy the full SHA
    2e006b2 View commit details
    Browse the repository at this point in the history

  4. Sync analysis_options.yaml with flutter/flutter (#11823) 

    Pulls in changes from flutter/flutter's analysis_options.yaml since the last since at the end of 2023.
- `invalid_runtime_check_with_js_interop_types` is disabled for now; see flutter/flutter#187454
- `dart fix --apply` has been run on all packages, which auto-fixed a lot of cases of `unnecessary_underscores`, and a handful of `avoid_final_parameters`
    @stuartmorgan-g
    stuartmorgan-g authored Jun 4, 2026
    Configuration menu
    Copy the full SHA
    c869a5d View commit details
    Browse the repository at this point in the history

  5. [tool] Use flutter for pub commands when examples use Flutter (#11830) 

    #11797 changed the repo tooling to use `dart` instead of `flutter` for more commands when the target package isn't a Flutter package, include `pub downgrade` and `pub get` in `analyze`. However, since `pub get` will resolve any example apps, if any of *them* use Flutter, `dart pub get` will fail unless `dart` is coming from the Flutter SDK. Normally this is fine since that's the expected setup, but for the head-head tests in dart-lang that run the repo analysis using the head version of Dart via the `--analysis-sdk` flag, using that version of Dart for pub commands breaks things.

This checks the example apps for Flutter dependencies to ensure that `dart pub` won't be used in cases where that can cause failures to resolve in the examples. This should be safe for core-packages, since core-packages should never use Flutter, even in examples.
    @stuartmorgan-g
    stuartmorgan-g authored Jun 4, 2026
    Configuration menu
    Copy the full SHA
    61bdbb4 View commit details
    Browse the repository at this point in the history
Loading