There was a typo in the markdown made in #187258, and this PR corrects it. On master this is being fixed in #187380.

This pull request is created by [automatic cherry pick workflow](https://github.com/flutter/flutter/blob/main/docs/releases/Flutter-Cherrypick-Process.md#automatically-creates-a-cherry-pick-request)
Please fill in the form below, and a flutter domain expert will evaluate this cherry pick request.

### Issue Link:
What is the link to the issue this cherry-pick is addressing?

#186161

### Impact Description:
What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)?
Does it impact development (ex. flutter doctor crashes when Android Studio is installed),
or the shipping of production apps (the app crashes on launch).
This information is for domain experts and release engineers to understand the consequences of saying yes or no to the cherry pick.

This is an infrastructure update to renew the Apple iOS development signing certificate used by the Chromium CI bots. The Chromium infrastructure team has already deployed the new certificate to the macOS bots. If this provisioning profile update is not cherry-picked to the stable branch, the bots will attempt to use the old provisioning profile with the new certificate, causing a signature mismatch.

### Changelog Description:
Explain this cherry pick:
* In one line that is accessible to most Flutter developers.
* That describes the state prior to the fix.
* That includes which platforms are impacted.
See [best practices](https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md) for examples.

Updates the iOS provisioning profile CIPD package used by CI bots to support the 2026-2027 code signing certificate.

Prior to this fix, the CI configuration referenced an older provisioning profile that does not trust the newly rotated iOS developer certificate.

Impacted platforms: Mac / iOS CI Infrastructure.

### Workaround:
Is there a workaround for this issue?

There is no workaround. The CI bots must use the updated provisioning profile to successfully sign and run iOS tests.

### Risk:
What is the risk level of this cherry-pick?

### Test Coverage:
Are you confident that your fix is well-tested by automated tests?

### Validation Steps:
What are the steps to validate that this fix works?

Ensure the presubmit CI checks for this PR pass successfully (specifically the Mac and Mac_arm64 test shards).

Verify in the dependencies section of a passing Mac Swarming task that it is downloading the version:to_2027 tag for apple_signing.

…-preview (#187323)

This pull request is created by [automatic cherry pick workflow](https://github.com/flutter/flutter/blob/main/docs/releases/Flutter-Cherrypick-Process.md#automatically-creates-a-cherry-pick-request)
Please fill in the form below, and a flutter domain expert will evaluate this cherry pick request.

### Issue Link:
What is the link to the issue this cherry-pick is addressing?

#187322

### Impact Description:
What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)?
Does it impact development (ex. flutter doctor crashes when Android Studio is installed),
or the shipping of production apps (the app crashes on launch).
This information is for domain experts and release engineers to understand the consequences of saying yes or no to the cherry pick.

This issue impacts development. When using `flutter widget-preview start`, if the Dart Tooling Daemon (DTD) is not running or fails to connect at startup, the tool crashes with an unhandled `RpcException` or `StateError` showing a full stack trace instead of exiting gracefully. Additionally, if the DTD connection is lost during an active session, the file-watching stream crashes, abruptly terminating the session.

### Changelog Description:
Explain this cherry pick:
* In one line that is accessible to most Flutter developers.
* That describes the state prior to the fix.
* That includes which platforms are impacted.
See [best practices](https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md) for examples.

[flutter/187322] When DTD connection is lost or fails at startup during widget-preview on all platforms, the tool crashes with unhandled exceptions instead of exiting gracefully.

### Workaround:
Is there a workaround for this issue?

Ensure that DTD is running and stable before starting `widget-preview`, and restart the tool if it crashes due to connection loss. There is no direct workaround to prevent the crash if the connection is lost.

### Risk:
What is the risk level of this cherry-pick?

### Test Coverage:
Are you confident that your fix is well-tested by automated tests?

### Validation Steps:
What are the steps to validate that this fix works?

1. **Startup Failure Validation:**
   * Run `flutter widget-preview start` in a project where DTD is not available or is forced to fail.
   * Verify that the tool exits cleanly with the message: `Failed to retrieve widget previews from the Dart Tooling Daemon (DTD). Ensure that the analysis server is running and reachable.` (instead of crashing with a stack trace).

2. **Connection Loss Validation:**
   * Run `flutter widget-preview start` and ensure it starts successfully.
   * Simulates DTD connection loss (e.g., by terminating the DTD process or the analysis server).
   * Verify that the tool logs a warning: `Lost connection to the Dart Tooling Daemon (DTD). Live preview updates are paused.` and does not crash the active session.

…ge-to-edge mode (#187276)

This pull request is created by [automatic cherry pick workflow](https://github.com/flutter/flutter/blob/main/docs/releases/Flutter-Cherrypick-Process.md#automatically-creates-a-cherry-pick-request)
Please fill in the form below, and a flutter domain expert will evaluate this cherry pick request.

### Issue Link:
What is the link to the issue this cherry-pick is addressing?

#186723

### Impact Description:
What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)?
Does it impact development (ex. flutter doctor crashes when Android Studio is installed),
or the shipping of production apps (the app crashes on launch).
This information is for domain experts and release engineers to understand the consequences of saying yes or no to the cherry pick.

Apps cannot switch from any [`SystemUiMode`](https://api.flutter.dev/flutter/services/SystemUiMode.html) to edge-to-edge mode.

### Changelog Description:
Explain this cherry pick:
* In one line that is accessible to most Flutter developers.
* That describes the state prior to the fix.
* That includes which platforms are impacted.
See [best practices](https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md) for examples.

[flutter/186723] When apps try to switch from any `SystemUiMode` to edge-to-edge on Android, the system bars incorrectly remain invisible.

### Workaround:
Is there a workaround for this issue?

As per #186723 (comment), you can restore edge-to-edge manually.

> As a workaround, I've found you can restore edge-to-edge like this: 
> ` SystemChrome.setEnabledSystemUIMode(
>        SystemUiMode.manual,
>        overlays: SystemUiOverlay.values,
>      ),`

### Risk:
What is the risk level of this cherry-pick?

### Test Coverage:
Are you confident that your fix is well-tested by automated tests?

### Validation Steps:
What are the steps to validate that this fix works?

Run the sample app in #186723 (comment) and attempt switching between `immersiveSticky` mode and `edge-to-edge`.

…187384)

This PR cherry-picks multiple commits due to the incremental nature of them. They all touch the same files and therefore have many merge conflicts in cherry-picked individually. 

### Issue Link:
What is the link to the issue this cherry-pick is addressing?

#186054, #185775

### Impact Description:
What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)?
Does it impact development (ex. flutter doctor crashes when Android Studio is installed),
or the shipping of production apps (the app crashes on launch).
This information is for domain experts and release engineers to understand the consequences of saying yes or no to the cherry pick.

iOS apps may fail to download SwiftPM dependencies, especially in CI.

Also, SwiftPM was printing warnings on non-iOS/macOS builds, which it shouldn't.

### Changelog Description:
Explain this cherry pick:
* In one line that is accessible to most Flutter developers.
* That describes the state prior to the fix.
* That includes which platforms are impacted.
See [best practices](https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md) for examples.

[flutter/186054] When building an iOS or macOS app with Swift Package Manager enabled, remote package dependencies may fail to download.
[flutter/185775] When building for non-iOS or macOS apps, Swift Package Manager warnings may appear.

### Workaround:
Is there a workaround for this issue?

Pin to an older version of Flutter or disable SwiftPM.

### Risk:
What is the risk level of this cherry-pick?

### Test Coverage:
Are you confident that your fix is well-tested by automated tests?

### Validation Steps:
What are the steps to validate that this fix works?

It's a race condition so it's not always consistent:
```
flutter config --no-enable-swift-package-manager
mkdir temp_workspace && cd temp_workspace
mkdir packages && cd packages
flutter create unmigrated_app && cd unmigrated_app
flutter pub add google_maps_flutter google_maps_flutter_ios_sdk10
echo "resolution: workspace" >> pubspec.yaml
cd ..
flutter config --enable-swift-package-manager
flutter create migrated_app && cd migrated_app
flutter pub add google_maps_flutter google_maps_flutter_ios_sdk10
flutter build ios --config-only
echo "resolution: workspace" >> pubspec.yaml
cd .. 
rm -rf build
cd ..
echo -e "name: _\npublish_to: none\nenvironment:\n  sdk: ^3.6.0\nworkspace:\n  - packages/unmigrated_app\n  - packages/migrated_app" >> pubspec.yaml
rm -rf $HOME/Library/Caches/org.swift.swiftpm
rm -rf $HOME/Library/org.swift.swiftpm
flutter pub get && cd packages/unmigrated_app && flutter build ios
```

…87790)

Added release notes for Flutter version 3.44.2. Part of #187786

If this change needs to override an active code freeze, provide a comment explaining why. The code freeze workflow can be overridden by code reviewers. See pinned issues for any active code freezes with guidance.

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

…4ae107a03b2b4e1d61c3bebe93 (#187788)

This PR updates the transitive dependencies in the engine `DEPS` file based on Dart SDK hash `d684a576a6aa954ae107a03b2b4e1d61c3bebe93`. Part of #187786

Part of #187786

If this change needs to override an active code freeze, provide a comment explaining why. The code freeze workflow can be overridden by code reviewers. See pinned issues for any active code freezes with guidance.

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