Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: flutter/flutter
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: b25305a8832c
Choose a base ref
...
head repository: flutter/flutter
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 6fba2447e95c
Choose a head ref
  • 11 commits
  • 22 files changed
  • 3 contributors

Commits on May 30, 2025

  1. [CP-Stable] Use Linux windows_*_engine orchestrators (#169772)

    Cherry-picks #168941.
    
    This is a pure infra change so release builds do not use a valuable Windows release builder just to spawn other builds.
    matanlurey authored May 30, 2025
    Configuration menu
    Copy the full SHA
    1091508 View commit details
    Browse the repository at this point in the history
  2. [CP-stable]🐛 Use consist slashes when generating dep files (#169630)

    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?
    
    #163591
    
    ### Changelog Description:
    
    Normalizes file paths in every depfile, especially on Windows. It eliminates the inconsistency that can occur when other codes find the file paths are different and produce unexpected results.
    
    ### Impact Description:
    
    The most noticeable impact so far is that people are unable to build flavored Android packages on Windows repeatedly until the next clean.
    
    ### Workaround:
    Is there a workaround for this issue?
    
    The workaround is to manually patch the project's gradle script: #163591 (comment)
    From my experience, the patch is not always working and is hard to maintain.
    
    ### 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?
    
    Follow the *steps to reproduce* section in #163591 (comment).
    flutteractionsbot authored May 30, 2025
    Configuration menu
    Copy the full SHA
    04f9ead View commit details
    Browse the repository at this point in the history

Commits on Jun 3, 2025

  1. [CP-stable] Split Linux docs_publish into `Linux docs_generate_rele…

    …ase` (#169912)
    
    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?
    
    #168913
    
    ### Changelog Description:
    Explain this cherry pick in one line that is accessible to most Flutter developers. See [best practices](https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md) for examples
    
    N/A - This is an internal infrastructure change.
    
    ### 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 production app (the app crashes on launch)
    
    No user impact, could negatively impact how API docs are published.
    
    ### Workaround:
    Is there a workaround for this issue?
    
    N/A
    
    ### 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?
    
    View post-submits when a stable release is published and verify API docs were published.
    flutteractionsbot authored Jun 3, 2025
    Configuration menu
    Copy the full SHA
    d88a675 View commit details
    Browse the repository at this point in the history
  2. Update engine.version for 3.32.2 stable hotfix release (#169952)

    Updates `engine.version` for 3.32.2 stable hotfix release to the last cherry-pick SHA: d88a675
    
    I think this is required because there were engine changes in a previous cherry-pick (#169772)  not included in the 3.32.1 stable hotfix release.
    camsim99 authored Jun 3, 2025
    Configuration menu
    Copy the full SHA
    fa17ad1 View commit details
    Browse the repository at this point in the history

Commits on Jun 4, 2025

  1. Re-update engine.version for 3.32.2 stable hotfix release to the la…

    …st SHA with engine change (#170005)
    
    Corrects `engine.version` for 3.32.2 stable hotfix release to the last cherry-pick SHA with an engine change: 
    1091508
    camsim99 authored Jun 4, 2025
    Configuration menu
    Copy the full SHA
    8defaa7 View commit details
    Browse the repository at this point in the history

Commits on Jun 5, 2025

  1. [CP-stable]Revert "Fix NavigationBar indicator overlay color (#164484)…

    …" (#170052)
    
    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?
    
    #169249
    #169436
    
    ### Changelog Description:
    Explain this cherry pick in one line that is accessible to most Flutter developers. See [best practices](https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md) for examples
    
    NavigationBar active indicator animation gets stucked.
    
    ### 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 production app (the app crashes on launch)
    
    Visual glitch visible by users. In several scenarios, the active indicator for NavigationBar and NavigationDrawer is not properly painted (animation stucked half way or active color not reflecting the current state).
    
    ### Workaround:
    Is there a workaround for this issue?
    
    No
    
    ### Risk:
    What is the risk level of this cherry-pick?
    
      - [ x ] Low
    
    ### Test Coverage:
    Are you confident that your fix is well-tested by automated tests?
    
      - [ x ] Yes
    
    ### Validation Steps:
    What are the steps to validate that this fix works?
    
    Run the code sample from #169249.
    This fix is a revert to a PR which landed in the current stable.
    flutteractionsbot authored Jun 5, 2025
    Configuration menu
    Copy the full SHA
    46a4c05 View commit details
    Browse the repository at this point in the history
  2. [CP-stable][Impeller] Maintain a global map of each context's current…

    …ly active thread-local command pools (#170013)
    
    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?
    
    #169208
    
    ### Changelog Description:
    Explain this cherry pick in one line that is accessible to most Flutter developers. See [best practices](https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md) for examples
    
    Fixes a memory leak in the Impeller Vulkan back end.
    
    ### 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 production app (the app crashes on launch)
    
    The memory usage of apps using Impeller/Vulkan will increase as frames are rendered.  Memory consumption will grow until the Android activity enters the stopped state.
    
    ### Workaround:
    Is there a workaround for this issue?
    
    Disabling Impeller
    
    ### Risk:
    What is the risk level of this cherry-pick?
    
      - [ x ] Medium
    
    ### Test Coverage:
    Are you confident that your fix is well-tested by automated tests?
    
      - [ x ] Yes
    
    ### Validation Steps:
    What are the steps to validate that this fix works?
    
    Start an app using Impeller/Vulkan that renders frames nonstop (for example, video playback).  Leave it running for several minutes.  Check memory metrics with a tool like `adb shell dumpsys meminfo` and verify that memory usage is stable.
    flutteractionsbot authored Jun 5, 2025
    Configuration menu
    Copy the full SHA
    31c4875 View commit details
    Browse the repository at this point in the history
  3. [CP-stable]fix: add the missing type of debug metadata (#170003)

    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?
    
    #169252
    
    ### Changelog Description:
    Explain this cherry pick in one line that is accessible to most Flutter developers. See [best practices](https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md) for examples
    
    Fixes a build failure on Android for app bundles when setting debug symbol level to `FULL` and using release mode.
    
    ### 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 production app (the app crashes on launch)
    
    Flutter fails to build an AAB in release mode.
    
    ### Workaround:
    Is there a workaround for this issue?
    
    No, besides not using this symbol level.
    
    ### 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?
    
    This linked issue has easy to follow repro steps for the original issue, which also function as validation steps that the issue is fixed.
    flutteractionsbot authored Jun 5, 2025
    Configuration menu
    Copy the full SHA
    b02643b View commit details
    Browse the repository at this point in the history

Commits on Jun 11, 2025

  1. Configuration menu
    Copy the full SHA
    5c14335 View commit details
    Browse the repository at this point in the history

Commits on Jun 12, 2025

  1. Trigger a new engine build from HEAD in 3.32 (#170558)

    Workaround for #170536.
    matanlurey authored Jun 12, 2025
    Configuration menu
    Copy the full SHA
    8cd19e5 View commit details
    Browse the repository at this point in the history

Commits on Jun 13, 2025

  1. Update engine.version (#170560)

    Workaround for #170536.
    matanlurey authored Jun 13, 2025
    Configuration menu
    Copy the full SHA
    6fba244 View commit details
    Browse the repository at this point in the history
Loading