…11225)

## Description

Adds support for screen auto-lock during video playback on iOS.

By default, the video player keeps the screen awake during playback. Some apps (e.g. login screens with background videos, ambient content) want the screen to be able to auto-lock while video plays. This PR adds an option to allow that behavior.

### Changes

* Add `preventsDisplaySleepDuringVideoPlayback` to `VideoPlayerOptions` (default: `true` to preserve existing behavior)
* When `false`, the screen can auto-lock during playback
* Implemented on iOS/macOS via `AVPlayer.preventsDisplaySleepDuringVideoPlayback`
* Platform interface: `setPreventsDisplaySleepDuringVideoPlayback(int playerId, bool preventsDisplaySleepDuringVideoPlayback)`

### Usage

```dart
VideoPlayerController.networkUrl(
  url,
  videoPlayerOptions: VideoPlayerOptions(preventsDisplaySleepDuringVideoPlayback: false),
);
```

## Breakout PRs

1. Platform interface: #11546
2. AVFoundation (iOS/macOS): #11547

## Issues fixed

* Fixes: [flutter/flutter#183520](flutter/flutter#183520) (How to disable wakelock on iOS side?)
* Addresses the need to allow screen auto-lock during video playback on iOS (e.g. for ambient/background videos)

## Pre-Review Checklist

…license headers (#12170)

This PR adds `#region` to example files to remove the license headers. 

Before:

<img width="738" height="710" alt="image" src="https://github.com/user-attachments/assets/04069857-c590-470e-9682-bc601071bbc7" />

After:

<img width="739" height="716" alt="image" src="https://github.com/user-attachments/assets/7face8b4-8f01-4c94-81a7-0bbdf26afd14" />

### Verification

I have audited all example files to ensure every file belongs to one of the following types:

* **Referenced in `material_ui` or `cupertino_ui`:** These have been updated in this PR to include the `#region` tags.
* **Not referenced and not for a Material/Cupertino widget:** These files have been removed in PR #12179.
* **Not referenced but for a Material/Cupertino widget:** The following two files remain, and we should consider adding them to the respective API documentation in the future:
```
material_ui/example/lib/selection_area/selection_area.1.dart
material_ui/example/lib/selection_area/selection_area.2.dart
```

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

…erial and used in Cupertino (#12197)

The `dartdoc` requires that `@macro` will only search `@template` from `dependencies` packages, not `dev_dependencies`. Before this PR, both Cupertino and Material have used macros defined in the other package, and this does not completely work because `cupertino_ui` only lists `material_ui` as a dev dependency. On the other hand, `material_ui` lists `cupertino_ui` as a dependency and we plan to keep this way for a long time due to support for adaptive widgets.

This PR hence solves this macro problem by migrating all malfunctioning macros to be defined in `cupertino_ui` instead.

The changes were made in a script written by Gemini.

### Known issue

Referencing breadcrumbs ("square brackets") from `material_ui` in `cupertino_ui` does not work for now. The result is non-blocking for now, where all widget names (such as `[Button]`) do not have hyperlinks but are simply backticks. This is likely because of dart-lang/sdk#62812. Simply put, `dartdoc` only checks in symbols from `material_ui` if `material_ui` is `import`ed somewhere at least once, which means `material_ui` must be a dependency (not a dev dependency) of `cupertino_ui`. If dart-lang/sdk#62812 can be fixed, a `docImport` would make `dartdoc` checks in symbols.

Also, this problem can be worsened as we develop next generation Cupertino widgets, since `cupertino_ui` is planning to remove the prefixes and therefore have widget name conflicts with `material_ui`, and  [`docImport` currently does not support `as`](dart-lang/sdk#56527). For example, if a widget in `cupertino_ui` refers to a `[Dialog]`, which dialog does it refer to? 

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

Converts the legacy tests for `shared_preferences_android` to Kotlin, so that the plugin is now consistently using Kotlin, instead of a mix of Java and Kotlin.

As with the non-test PR, this was a first-pass conversion via the Android Studio auto-converted, followed by manual fixup, followed by running it through a local Gemini review focusing on making the Kotlin more idiomatic.

Follow-up to #12139
Part of flutter/flutter#188630

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

This declares support for analyzer versions 13.x in the `go_router_builder` package.

I ran `tool/run_tests.dart` after upgrading, no code changes are necessary and existing tests pass. Note that another package in this repository, `pigeon`, also depends on an older `analyzer` version but would require code changes to support analyzer version 13.x.

Closes flutter/flutter#189357.

## Pre-Review Checklist

Comments below:

- There is no relevant documentation to update.
- This change is covered by existing tests, so I have not added new ones.

flutter/flutter@cf9e8af...846664b

2026-07-14 [email protected] Roll Skia from dfcff99566c3 to 88954ef8f36d (1 revision) (flutter/flutter#189440)
2026-07-14 [email protected] refactor: remove material import from scrollable_semantics_test and selectable_region_context_menu_test (flutter/flutter#186611)
2026-07-14 [email protected] Roll Skia from 3d1fc554f1a2 to dfcff99566c3 (17 revisions) (flutter/flutter#189428)
2026-07-14 [email protected] Roll Dart SDK from 2c587df8f05a to 05bf153370c4 (5 revisions) (flutter/flutter#189426)
2026-07-14 [email protected] [flutter_tools] Remove web hot reload flag (flutter/flutter#185994)
2026-07-14 [email protected] [iOS] Fix flaky keyboard animation test (flutter/flutter#189353)
2026-07-14 [email protected] [Impeller] Playground expanded role (flutter/flutter#188889)
2026-07-14 [email protected] Roll pub packages (flutter/flutter#189409)
2026-07-13 [email protected] Update lock-threads dependency to 6.0.2 (flutter/flutter#189053)
2026-07-13 49699333+dependabot[bot]@users.noreply.github.com Bump actions/labeler from 6.1.0 to 6.2.0 in the all-github-actions group (flutter/flutter#189396)
2026-07-13 [email protected] Remove  outdated todo about `analysis bug on Windows` and update condition to also perform `analysis on windows` (flutter/flutter#189283)
2026-07-13 [email protected] Add more 0x0 size tests part 4 (flutter/flutter#185187)
2026-07-13 [email protected] Roll Packages from 20928d5 to ad2eab1 (18 revisions) (flutter/flutter#189387)
2026-07-13 [email protected] [flutter_tools] Fix ADB device listing output parsing regression (flutter/flutter#189369)
2026-07-13 [email protected] Stop running most Mac x64 builders that have Mac ARM equivalents on master (flutter/flutter#189301)
2026-07-13 [email protected] Move a few benchmarks from x64 Intel Macs to ARM (flutter/flutter#189377)
2026-07-13 [email protected] Add note that `hcpp` needs impeller (flutter/flutter#189382)
2026-07-13 [email protected] Roll Fuchsia Linux SDK from vhIlDkWIy21IrlB9E... to oOETA0ISPouDt2xBo... (flutter/flutter#189349)
2026-07-13 [email protected] [flutter_tools] Respect mustMatchAppBuild on Windows native assets (flutter/flutter#186788)
2026-07-13 [email protected] Roll Skia from 8bf65996caba to 3d1fc554f1a2 (2 revisions) (flutter/flutter#189350)
2026-07-13 [email protected] Roll Dart SDK from 0fc1668c4af4 to 2c587df8f05a (9 revisions) (flutter/flutter#189351)
2026-07-13 [email protected] [web] Fall back to full CJK fonts for characters not covered by split slices (flutter/flutter#188890)
2026-07-13 [email protected] Take Mac tool_integration_tests_* out of bringup (flutter/flutter#189368)
2026-07-13 [email protected] [hooks] Roll record_use to 1.0 and unpin (flutter/flutter#189366)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-packages
Please CC [email protected],[email protected] on the revert to ensure that a human
is aware of the problem.

To file a bug in Packages: https://github.com/flutter/flutter/issues/new/choose

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

…2195)

Updated all Flutter Android plugin example apps to align with newer template versions for the Flutter 3.47 release.

Partially Addresses: flutter/flutter#189381
Related to: flutter/flutter#189380

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

Extract Config from google_fonts_all_parts.dart to google_fonts_config.dart. Rename Config to GoogleFontsConfig to avoid namespace clutter. Add a deprecated Config typedef for backward compatibility. Export GoogleFontsConfig and the deprecated Config in lib/google_fonts.dart. Bump package version to 8.2.0.

Unblocks #11433

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