Tags from packages

camera-v0.12.0+1: [camera] Make Optional.of constructor const (#11247)

2026-03-19T15:06:43Z

[camera] Make Optional.of constructor const (#11247)

Resolves old TODO from 2023 ( 6e09f5b committed by @camsim99 ) by making the `Optional.of` constructor `const` and removing the obsolete runtime `ArgumentError.checkNotNull` guard that was only needed during Dart 2's mixed-mode (unsound null safety) era. Mixed-mode execution was removed in Dart 3.0, so this is dead code. Not a breaking change.

Note that the entire `Optional<T>` class (and surrounding `CameraController`) is copy-pasted across 4 files in the camera packages. Would you prefer to move `Optional<T>` into `camera_platform_interface` to share it, or replace it entirely e.g. with a private sentinel pattern in `copyWith` (as the Flutter framework does for `ThemeData`)?

## Pre-Review Checklist

webview_flutter_wkwebview-v3.24.1

2026-03-18T18:26:17Z

[webview_flutter_wkwebview] Updates platform views on iOS to only hav…

…e a weak reference to the native view (#11175)

Updates `PlatformViewImpl` to only store a weak reference to the native view. This [issue](flutter/flutter#168535) seems to indicate the `PlatformViewsController` is keeping a reference to the native view even after it is removed from the `InstanceManager` in `webview_flutter_wkwebview`. This change should allow the pigeon call to happen when the reference to the Dart instance is deallocated. This should be safe because if the Dart instance is deallocated, then the Widget tree should no longer contain the PlatformView. And therefore the native UIView should no longer need to be used. Nor any callbacks that need the `UIView` since it is not on screen.

Potential fix for flutter/flutter#168535, but should still update engine to notify plugins that they are detached before setting `PlatformViewsController` to nil.

## 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.

local_auth_android-v2.0.7

2026-03-18T20:24:23Z

[local_auth] Convert to Kotlin gradle for the plugin build files (#11169

)

Following up from #11127, this is the initial example of converting a plugin build, rather than an example app build, to Kotlin gradle.

This conversion was done manually, but closely referencing the current plugin template files. It differs mostly in not having the parts that are specific to the use of Kotlin source files, since `local_auth` is still Java-only. Later (when we start adopting Kotlin Pigeon generation everywhere, for instance) some of the diffs relative to the template files will go away.

Unlike #11127 this did not require tool changes, as it turns out that the previous changes were enough to handle these files, but I did add more tests. As with #11127 I did not attempt to comprehensively duplicate all Groovy tests, since we should be able to relatively quickly convert everything in the repo, and then pull out the Groovy support and update all the tests to Kotlin.

Note that this does *not* convert the plugin's example app to Kotlin gradle, only the plugin itself. The example app for plugins are non-trivial enough (due to native tests) that they should be converted separately. This has the bonus effect of validating that the plugin migration didn't require any changes in the client app.

Part of flutter/flutter#176065

## 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.

local_auth_android-v2.0.6

2026-03-18T18:24:37Z

[dependabot]: Bump androidx.core:core from 1.17.0 to 1.18.0 in /packa…

…ges/local_auth/local_auth_android/android (#11256)

Bumps androidx.core:core from 1.17.0 to 1.18.0.

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=androidx.core:core&package-manager=gradle&previous-version=1.17.0&new-version=1.18.0)](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 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>

interactive_media_ads-v0.3.0+12

2026-03-18T18:16:39Z

[dependabot]: Bump androidx.core:core-ktx from 1.13.0 to 1.18.0 in /p…

…ackages/interactive_media_ads/android (#11255)

Bumps androidx.core:core-ktx from 1.13.0 to 1.18.0.

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=androidx.core:core-ktx&package-manager=gradle&previous-version=1.13.0&new-version=1.18.0)](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 />

</details>

google_maps_flutter-v2.16.0

2026-03-18T19:08:08Z

[google_maps_flutter] Add color scheme support to app-facing package (#…

…11280)

App-facing portion of #10471, incorporating review feedback and some other minor cleanup.

Fixes flutter/flutter#176445

## 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.

google_maps_flutter_web-v0.6.2

2026-03-18T15:47:12Z

[google_maps_flutter] Add color scheme support to web implementation (#…

…11279)

Web portion of #10471, incorporating review feedback and some other minor cleanup.

Part of flutter/flutter#176445

## 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.

google_maps_flutter_platform_interface-v2.15.0

2026-03-18T13:55:36Z

[google_maps_flutter] Add color scheme support to platform interface (#…

…11278)

Platform interface portion of #10471

Part of flutter/flutter#176445

## 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.

google_maps_flutter_android-v2.19.3: [google_maps_flutter_android] Batch clustered marker operations (#10940)

2026-03-18T15:35:04Z

[google_maps_flutter_android] Batch clustered marker operations (#10940)

Note: this PR attempts to use the same strategy from the Google Maps Flutter Web PR #10562 and apply it to Google Maps Flutter Android.

## Summary
- Adds batch `addItems()` and `removeItems()` methods to `ClusterManagersController`
- Refactors `MarkersController` to batch add/remove/change operations for clustered markers
- Reduces redundant re-clustering calls when multiple markers are added/removed/changed at once

This improves performance when working with large numbers of clustered markers by calling `ClusterManager.cluster()` once per cluster manager instead of once per marker.

## Test plan
- Added unit tests for batch add/remove operations
- Added unit test for batch cluster manager changes
- Existing tests pass

Addresses flutter/flutter#170573

## 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.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

web_benchmarks-v4.1.1: [web_benchmark] Fix tab connection for newer versions of Chrome (#11266)

2026-03-17T18:15:12Z

[web_benchmark] Fix tab connection for newer versions of Chrome (#11266)

DevTools has been experiencing a [flake](flutter/flutter#183335) with `package:web_benchmark`'s launching of Chrome. I've also noticed several times a similar failure when running web engines locally.

Turns out (from trial and error) that newer versions of Chrome seem to establish the WIP connection before tabs have had a chance to open. It's a race between the two, and when the WIP connections is faster, we fail to find any tab to connect to, and therefore we fail. The fix in this PR is to allow a grace period of 5 seconds of retrying to find the tab.

I made a [similar fix](flutter/flutter#183737) in the flutter/flutter repo.