Zizmor was flagging this failure in another review. 
Agent suggested deleting this line since the following line does the same thing and I agree. 
Secondary validation will be this pr passing presubmit. 

## Pre-Review Checklist

- [] I followed [the version and CHANGELOG instructions], using [semantic versioning] and the [repository CHANGELOG style], or I have commented below to indicate which documented exception this PR falls under[^1].

Adds a new "promote" keyword recognized by the batch release changelog processor, which allows for a pre-1.0 package to be promoted to 1.0 using the usual batch release process.

…2199)

Fixes flutter/flutter#186933

`SvgParser.parseFontWeight` throws on any value outside the recognized CSS
keywords and numeric weights. That makes the whole SVG fail to compile for
non-standard values such as `font-weight="regular"`.

This change treats an unrecognized value as an invalid declaration: it emits a
warning and returns no parsed value, so normal style inheritance still applies.
An unstyled root therefore keeps the initial normal weight, while an invalid
child declaration no longer overrides a bold parent. Strict
`warningsAsErrors` builds continue to throw.

Tests cover an unrecognized root value, inheritance from a bold parent, and the
warnings-as-errors path. `flutter analyze` and the full 333-test
`vector_graphics_compiler` suite pass locally.

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

flutter/flutter@9988960...0f02463

2026-07-28 [email protected] Roll Fuchsia Test Scripts from E8hJ1AfK8CtGtaES0... to 1frGe_KltAJKkeyPg... (flutter/flutter#190134)
2026-07-28 [email protected] iOS: Reject merged-platform-ui-thread=mergeAfterLaunch (flutter/flutter#190051)
2026-07-28 [email protected] iOS: Migrate TaskRunner tests to Swift Testing (flutter/flutter#190055)
2026-07-28 [email protected] Run Mac golden tests on ARM bots (flutter/flutter#189465)
2026-07-28 [email protected] iOS,macOS: Rename Swift test files to end in Tests.swift (flutter/flutter#190063)
2026-07-28 [email protected] Fix hcpp cliprect being behind by 1 frame when scrolling (flutter/flutter#189946)
2026-07-28 [email protected] Roll Fuchsia Linux SDK from vpboK5fPPIoFteqRq... to OZkZC_2CZ_G5rbMIS... (flutter/flutter#190115)
2026-07-27 [email protected] Add Ishaq Hassan to AUTHORS (flutter/flutter#190064)
2026-07-27 [email protected] [wimp] fixes ubo padding size issue (flutter/flutter#189958)
2026-07-27 [email protected] Roll pub packages (flutter/flutter#189872)
2026-07-27 [email protected] Move tool host_cross_arch tests into different shards (flutter/flutter#189470)
2026-07-27 49699333+dependabot[bot]@users.noreply.github.com Bump actions/labeler from 6.2.0 to 7.0.0 in the all-github-actions group (flutter/flutter#190099)
2026-07-27 [email protected] [ios]do not nuke user input path when running uiscene integration test (flutter/flutter#186436)
2026-07-27 [email protected] ci: verify_binaries_pre_codesigned part 2 (flutter/flutter#190078)
2026-07-27 [email protected] Roll Abseil to ff6e8ce3e932 (flutter/flutter#189998)
2026-07-27 [email protected] Android_hardware_smoke_test: clean up golden copy in CI (flutter/flutter#189948)

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] 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

Deletes `GeneratedCameraxLibrary.java` which is the pre-#8618 (migration to `ProxyApis`) pigeon code that the plugin used. It appears to no longer be used.

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

Fix doc references in material_ui and cupertino_ui
Towards flutter/flutter#189629

I also commented out youtube directives since they do not work outside of the SDK.

There are some references we cannot fix in the design packages themselves, largely due tot he fact that material_ui and cupertino_ui export the widgets library. That pulls in doc references from the widgets library that cannot be resolved outside of the scope of the SDK.

We can change the doc upstream in the SDK, but that feel like a poor choice to make the docs less helpful in the SDK in order to resolve a reference issue in a downstream package.
Something we are planning for after the initial 1.0 is to remove the export of widgets from both packages, which will resolve the remaining issues.

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

See flutter/flutter#189629.

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

This pr is blocked by #12298. 

This came up in #12297. I decided landing the tool focused pr was much easier to review than stacking this work on #12285 - @reidbaker 

---
Agent authored pr description
This PR exempts .agents and evals directories from triggering missing changelog and version update errors.

TAG=agy
CONV=24c0c9b5-7e8d-407c-ae84-a577061bd6ff

Updates the iOS and macOS Swift unit tests to use Swift Testing rather than XCTest.

Part of flutter/flutter#180787

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

… deep links (#12213)

When `onEnter` returns `Block.stop()` on the very first navigation attempt (e.g. a deep link on web, before any route has been committed), the parser's `onCanNotEnter` path has no prior configuration to restore and reports a generic `GoException`. Apps handling this in `onException` can't tell "initial deep link blocked" apart from other routing errors (unmatched routes, redirect loops) without string matching on the exception message.

This adds `BlockedInitialNavigationException extends GoException`, raised specifically in that no-prior-route path. It only refines the exception type — no change to when or whether an exception is thrown, and existing `is GoException` checks keep working. Apps can now write `if (state.error is BlockedInitialNavigationException)` in `onException` and, for example, redirect to a loading screen with the deep link preserved instead of treating it as a 404.

Test: widget test in `on_enter_test.dart` — initial navigation blocked by `Block.stop()` with an `onException` handler; asserts the captured `state.error` is a `BlockedInitialNavigationException` (and still a `GoException`).

Fixes flutter/flutter#189581

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

Now that the new APIs are available on stable, remove the view controller subclass workaround and use the standard scene-friendly registration system for channel code.