Update breaking change index for 3.38 (#12625)

Author: parlough

site/lib/src/style_hash.dart

@@ -2,4 +2,4 @@
 // dart format off
 
 /// The generated hash of the `main.css` file.
-const generatedStylesHash = 'nvTevrLjFn98';
+const generatedStylesHash = 'zhB0VEJdy4va';

src/content/release/breaking-changes/deprecate-focusable.md

@@ -12,36 +12,39 @@ The `SemanticsProperties.focusable` and `SemanticsConfiguration.isFocusable`
 parameters were deprecated in favor of the `SemanticsProperties.focused` and
 `SemanticsConfiguration.isFocused` parameters.
 
-The `focused` parameter is now nullable. Setting it to `true` or `false`
-automatically sets `isFocusable` to `true`, while setting it to `null`
-sets `isFocusable` to `false`.
+The `focused` parameter is now nullable.
+Setting it to `true` or `false` automatically
+sets `isFocusable` to `true`, while
+setting it to `null` sets `isFocusable` to `false`.
 
 ## Context
 
-The `SemanticsConfiguration.isFocusable` property is a boolean that indicates
-whether the semantics node can have input focus, and
-
+The `SemanticsConfiguration.isFocusable` property is a boolean that
+indicates whether the semantics node can have input focus.
 `SemanticsConfiguration.isFocused` is a boolean that indicates if the
 semantics node has input focus.
 
-This change also applies to `SemanticsProperties.focusable` and `SemanticsProperties.focused`.
+This change also applies to
+`SemanticsProperties.focusable` and `SemanticsProperties.focused`.
 
 We deprecated `isFocusable` because its functionality is covered by `isFocused`.
 The `isFocused` property is now stored as a tristate flag in the engine,
 and this change makes the framework consistent with the engine.
 
 ## Description of change
 
-The `SemanticsConfiguration.isFocusable` property is deprecated in
-favor of `SemanticsConfiguration.isFocused`. This property is a nullable
-boolean; setting it to `true` or `false` automatically sets `isFocusable` to
-`true`, and setting it to `null` sets `isFocusable` to `false`.
+The `SemanticsConfiguration.isFocusable` property is
+deprecated in favor of `SemanticsConfiguration.isFocused`.
+This property is a nullable boolean; setting it to `true` or `false`
+automatically sets `isFocusable` to `true`, and
+setting it to `null` sets `isFocusable` to `false`.
 
 ## Migration guide
 
-Replace `SemanticsConfiguration.isFocusable` with `SemanticsConfiguration.isFocused`.
+Replace `SemanticsConfiguration.isFocusable` with
+`SemanticsConfiguration.isFocused`.
 
-### Example 1: setting `isFocused` to `true` automatically sets `isFocusable` to `true`.
+### Example 1: Setting `isFocused` to `true` automatically sets `isFocusable` to `true`
 
 Code before migration:
 
@@ -60,7 +63,7 @@ void describeSemanticsConfiguration(SemanticsConfiguration config) {
 }
 ```
 
-### Example 2: setting `isFocused` to null automatically sets `isFocusable` to `false`.
+### Example 2: Setting `isFocused` to `null` automatically sets `isFocusable` to `false`
 
 Code before migration:
 
@@ -82,8 +85,8 @@ void describeSemanticsConfiguration(SemanticsConfiguration config) {
 
 ## Timeline
 
-Landed in version: 3.37.0-0.0.pre
-In stable release: Not yet
+Landed in version: 3.37.0-0.0.pre<br>
+In stable release: 3.38
 
 
 ## References

src/content/release/breaking-changes/deprecate-overlay-portal-targets-root.md

@@ -13,18 +13,20 @@ replaced with `overlayLocation`.
 
 ## Context
 
-A parameter `overlayLocation` was added to the OverlayPortal default constructor to
-control where the overlay child renders. As the result, the constructor
-`OverlayPortal.targetsRootOverlay` was no longer useful.
+A `overlayLocation` parameter was added to
+the `OverlayPortal` default constructor to
+control where the overlay child renders.
+As a result, the `OverlayPortal.targetsRootOverlay` constructor is
+no longer useful.
 
 ## Description of change
 
-The `OverlayPortal.targetsRootOverlay` was deprecated.
+The `OverlayPortal.targetsRootOverlay` constructor is deprecated.
 
 ## Migration guide
 
-If you are using `OverlayPortal.targetsRootOverlay`, you can use `OverlayPortal` with
-`overlayLocation` instead.
+If you are using `OverlayPortal.targetsRootOverlay`,
+use `OverlayPortal` with `overlayLocation` instead.
 
 ### Case 1: trivial case
 
@@ -42,7 +44,7 @@ Widget build(BuildContext context) {
 
 Code after migration:
 
-```dart
+```dart highlightLines=3
 Widget build(BuildContext context) {
   return OverlayPortal(
     overlayLocation: OverlayChildLocation.rootOverlay,
@@ -55,8 +57,8 @@ Widget build(BuildContext context) {
 
 ## Timeline
 
-Landed in version: 3.35.0-0.0.pre<br>
-In stable release: TBD
+Landed in version: 3.38.0-0.1.pre<br>
+In stable release: 3.38
 
 ## References
 

src/content/release/breaking-changes/font-weight-variation.md

@@ -56,7 +56,7 @@ to restore the font's default weight, set `fontWeight` to `FontWeight.normal`.
 
 ## Timeline
 
-Landed in version: 3.38.0-0.0.pre
+Landed in version: 3.39.0-0.0.pre<br>
 In stable release: Not yet
 
 ## References

src/content/release/breaking-changes/index.md

@@ -36,25 +36,30 @@ They're sorted by release and listed in alphabetical order:
 
 ### Not yet released to stable
 
+* [`FontWeight` also controls the weight attribute of variable fonts][]
+* [UISceneDelegate adoption][]
+* [`$FLUTTER_ROOT/version` replaced by `$FLUTTER_ROOT/bin/cache/flutter.version.json`][]
+* [Stop generating `AssetManifest.json`][]
+* [Deprecate `TextField.canRequestFocus`][]
+
+[`FontWeight` also controls the weight attribute of variable fonts]: /release/breaking-changes/font-weight-variation
+[UISceneDelegate adoption]: /release/breaking-changes/uiscenedelegate
+[Stop generating `AssetManifest.json`]: /release/breaking-changes/asset-manifest-dot-json
+[`$FLUTTER_ROOT/version` replaced by `$FLUTTER_ROOT/bin/cache/flutter.version.json`]: /release/breaking-changes/flutter-root-version-file
+[Deprecate `TextField.canRequestFocus`]: /release/breaking-changes/can-request-focus
+
+<a id="released-in-flutter-338" aria-hidden="true"></a>
+### Released in Flutter 3.38
+
 * [`CupertinoDynamicColor` wide gamut support][]
 * [Deprecate `OverlayPortal.targetsRootOverlay`][]
 * [Deprecate `SemanticsProperties.focusable` and `SemanticsConfiguration.isFocusable`][]
-* [Deprecate `TextField.canRequestFocus`][]
-* [`$FLUTTER_ROOT/version` replaced by `$FLUTTER_ROOT/bin/cache/flutter.version.json`][]
-* [`FontWeight` also controls the weight attribute of variable fonts][]
 * [SnackBar with action no longer auto-dismisses][]
-* [Stop generating `AssetManifest.json`][]
-* [UISceneDelegate adoption][]
 
 [`CupertinoDynamicColor` wide gamut support]: /release/breaking-changes/wide-gamut-cupertino-dynamic-color
 [Deprecate `OverlayPortal.targetsRootOverlay`]: /release/breaking-changes/deprecate-overlay-portal-targets-root
 [Deprecate `SemanticsProperties.focusable` and `SemanticsConfiguration.isFocusable`]: /release/breaking-changes/deprecate-focusable
-[Deprecate `TextField.canRequestFocus`]: /release/breaking-changes/can-request-focus
-[`$FLUTTER_ROOT/version` replaced by `$FLUTTER_ROOT/bin/cache/flutter.version.json`]: /release/breaking-changes/flutter-root-version-file
-[`FontWeight` also controls the weight attribute of variable fonts]: /release/breaking-changes/font-weight-variation
 [SnackBar with action no longer auto-dismisses]: /release/breaking-changes/snackbar-with-action-behavior-update
-[Stop generating `AssetManifest.json`]: /release/breaking-changes/asset-manifest-dot-json
-[UISceneDelegate adoption]: /release/breaking-changes/uiscenedelegate
 
 <a id="released-in-flutter-335" aria-hidden="true"></a>
 ### Released in Flutter 3.35

src/content/release/breaking-changes/snackbar-with-action-behavior-update.md

@@ -9,37 +9,42 @@ description: >-
 
 ## Summary
 
-The default behavior of a [`SnackBar`][] with an action has changed. Previously, a
-`SnackBar` with an action would not auto-dismiss if talkback was enabled.
-Now, all `SnackBar`s with an action default to a non-dismissible state until the
-user interacts with the action button.
+The default behavior of a [`SnackBar`][] with an action has changed.
+Previously, a `SnackBar` with an action wouldn't
+auto-dismiss if talkback was enabled.
+Now, all `SnackBar` widgets with an action default to
+a non-dismissible state until the user interacts with the action button.
 
 ## Context
 
-A `SnackBar` with an action button is now treated as a more persistent
-notification that requires user interaction. This change improves accessibility
-and user experience by ensuring that critical notifications remain on the screen
-until they are acknowledged.
+A `SnackBar` with an action button is now treated as
+a more persistent notification that requires user interaction.
+This change improves accessibility and user experience by ensuring that
+critical notifications remain on the screen until they are acknowledged.
 
 ## Description of change
 
-This change aligns with the Material 3 design specifications for `SnackBar`s:
+This change aligns with the Material 3 design specification for
+the `SnackBar` component:
+
 * Old behavior: A `SnackBar` with an action button would auto-dismiss after a
   duration unless talkback was enabled.
 * New behavior: A `SnackBar` with an action button won't auto-dismiss;
-   it remains on screen until dismissed by the user.
+  it remains on screen until dismissed by the user.
 
 To override this behavior, an optional `persist` property has
-been added to `SnackBar`. When `persist` is true, the `SnackBar` won't auto-dismiss
-and remains on screen until manually dismissed by the user. When false, the
-`SnackBar` auto-dismisses after its standard duration, regardless of the
-presence of an action. When null, the `SnackBar` follows the default
-behavior, which won't auto-dismiss if an action is present.
+been added to `SnackBar`.
+When `persist` is `true`, the `SnackBar` won't auto-dismiss and
+remains on screen until manually dismissed by the user.
+When `false`, the `SnackBar` auto-dismisses after its standard duration,
+regardless of the presence of an action.
+When `null`, the `SnackBar` follows the default behavior,
+which won't auto-dismiss if an action is present.
 
 ## Migration guide
 
 To restore the old auto-dismiss behavior for a SnackBar with an action, set
-`persist` to false.
+`persist` to `false`.
 
 Code before migration:
 
@@ -59,7 +64,7 @@ ScaffoldMessenger.of(context).showSnackBar(
 
 Code after migration:
 
-```dart
+```dart highlightLines=4
 ScaffoldMessenger.of(context).showSnackBar(
   SnackBar(
     content: const Text('This is a snackbar with an action.'),
@@ -76,8 +81,8 @@ ScaffoldMessenger.of(context).showSnackBar(
 
 ## Timeline
 
-Landed in version: TBD
-In stable release: TBD
+Landed in version: 3.37.0-0.0.pre
+In stable release: 3.38
 
 ## References
 

src/content/release/breaking-changes/wide-gamut-cupertino-dynamic-color.md

@@ -15,10 +15,10 @@ added in [Flutter 3.27][Migration guide for wide gamut Color].
 
 ## Context
 
-The `Color` class was updated to support wide gamut color spaces, but some
-corresponding deprecations were not initially applied to
-`CupertinoDynamicColor` due to its implementation rather than due to
-the extension of `Color`.
+The `Color` class was updated to support wide gamut color spaces,
+but some corresponding deprecations were not initially applied to
+`CupertinoDynamicColor` due to its implementation rather than
+due to the extension of `Color`.
 
 ## Description of change
 
@@ -55,12 +55,12 @@ final intBlue = _floatToInt8(color.b);
 
 ### Opacity
 
-Before Flutter 3.27, `Color` had the concept of "opacity", which showed up in the
-methods `opacity` and `withOpacity()`. Since Flutter 3.27, alpha is stored as a
-floating-point value. Using `.a` and `.withValues()` will give the full
-expression of a floating-point value and won't be quantized (restricted to a
-limited range). That means "alpha" expresses the intent of "opacity" more
-correctly.
+Before Flutter 3.27, `Color` had the concept of "opacity", which
+showed up in the methods `opacity` and `withOpacity()`.
+Since Flutter 3.27, the alpha channel has been stored as a floating-point value.
+Using `.a` and `.withValues()` will give the full expression of
+a floating-point value and won't be quantized (restricted to a limited range).
+That means "alpha" expresses the intent of "opacity" more correctly.
 
 #### Migrate `opacity`
 
@@ -85,8 +85,8 @@ final x = color.withValues(alpha: 0.5);
 
 ## Timeline
 
-Landed in version: Not yet<br>
-Stable release: Not yet
+Landed in version: 3.36.0-0.1.pre<br>
+Stable release: 3.38
 
 ## References
 

src/content/release/release-notes/index.md

@@ -12,6 +12,10 @@ For information about bug-fix releases,
 check out the Flutter [CHANGELOG][].
 :::
 
+* 3.38.0 _(Tentative)_
+  {% comment %} * [3.38.0 announcement][] {% endcomment %}
+  {% comment %} * [3.38.0 release notes & change log][] {% endcomment %}
+  * [3.38.0 breaking changes & migrations][]
 * 3.35.0
   * [3.35.0 announcement][]
   * [3.35.0 release notes & change log][]
@@ -101,6 +105,7 @@ check out the Flutter [CHANGELOG][].
 * Earlier
   * [Archived release notes][]
 
+[3.38.0 breaking changes & migrations]: /release/breaking-changes#released-in-flutter-3-38
 [3.35.0 announcement]: {{site.flutter-blog}}/whats-new-in-flutter-3-35-c58ef72e3766
 [3.35.0 release notes & change log]: /release/release-notes/release-notes-3.35.0
 [3.35.0 breaking changes & migrations]: /release/breaking-changes#released-in-flutter-3-35