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/packages
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 582f0e714974
Choose a base ref
...
head repository: flutter/packages
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: b04f3e5222a8
Choose a head ref
  • 6 commits
  • 29 files changed
  • 5 contributors

Commits on Mar 30, 2026

  1. [ci] Uses fluttergithubbot to create branches and PRs (#11368)

    The workflow needs a PAT that has signed CLA, otherwise, their pr won't pass ci
    
    ## 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.
    chunhtai authored Mar 30, 2026
    Configuration menu
    Copy the full SHA
    f1cdf0b View commit details
    Browse the repository at this point in the history
  2. [vector_graphic] docs: corrected width/height description in VectorGr…

    …aphic (#11361)
    
    Corrected the documentation for width and height parameters in the VectorGraphic widget.
    
    Fixes flutter/flutter#184116
    
    ## Pre-Review Checklist
    
    Test exemption: this is a documentation-only change.
    
    **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.
    eflat64 authored Mar 30, 2026
    Configuration menu
    Copy the full SHA
    6aec00b View commit details
    Browse the repository at this point in the history
  3. [google_maps_flutter] Add missing exports (#11196)

    This adds exports that should have been in #7882, but I missed in review.
    
    Like much of the `google_maps_flutter` APIs currently, advanced markers rely on clients using types that are defined in the platform interface package. This re-exports them, and fixes the examples to not import the platform interface.
    
    Ideally we would have more separation between the API layers, but this is deeply ingrained in the API design of the plugin at this point, so changing it would require a comprehensive overhaul.
    
    ## 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.
    stuartmorgan-g authored Mar 30, 2026
    Configuration menu
    Copy the full SHA
    4f94ee2 View commit details
    Browse the repository at this point in the history
  4. [pigeon] Reduces lint rules ignored in generated Dart code (#11230)

    When I landed #11149, which
    changes the `ignore_for_file` to use `type=lint`, I didn't examine the
    list of lint rules we _used to_ violate. In particular, since
    #11114 and
    #11163 landed, our generated
    code no longer violates the following rules:
    
    * unnecessary_parenthesis
    * prefer_null_aware_operators
    * unnecessary_import
    * no_leading_underscores_for_local_identifiers
    
    I believe this does not need CHANGELOG notes because users should not be
    using the _hidden_ 'ignore-lints' flag. This list of individually
    ignored lint rules should only appear in our tests or our checked-in
    generated Dart files.
    
    ## Pre-Review Checklist
    
    - [x] I read the [Contributor Guide] and followed the process outlined
    there for submitting PRs.
    - [x] I read the [AI contribution guidelines] and understand my
    responsibilities, or I am not using AI tools.
    - [ ] I read the [Tree Hygiene] page, which explains my
    responsibilities.
    - [x] I read and followed the [relevant style guides] and ran [the
    auto-formatter].
    - [x] I signed the [CLA].
    - [x] The title of the PR starts with the name of the package surrounded
    by square brackets, e.g. `[shared_preferences]`
    - [ ] I [linked to at least one issue that this PR fixes] in the
    description above.
    - [x] 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].
    - [ ] I updated/added any relevant documentation (doc comments with
    `///`).
    - [x] I added new tests to check the change I am making, or I have
    commented below to indicate which [test exemption] this PR falls
    under[^1].
    - [x] All existing and new tests are passing.
    
    Co-authored-by: stuartmorgan-g <stuartmorgan@google.com>
    srawlins and stuartmorgan-g authored Mar 30, 2026
    Configuration menu
    Copy the full SHA
    eab1265 View commit details
    Browse the repository at this point in the history
  5. [ci] Add permission to release_from_branches.yml (#11397)

    when the  caller workflow (release_from_branches.yml ) calls reusable_release.yml, the reusable workflow cannot have more permissions than the caller.
    
    ## 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.
    hannah-hyj authored Mar 30, 2026
    Configuration menu
    Copy the full SHA
    1de9829 View commit details
    Browse the repository at this point in the history
  6. [ci] Compares commits before creating a sync PR to sync release branc…

    …h back to the main branch. (#11398)
    
    fix the error: `pull request create failed: GraphQL: No commits between main and release-go_router (createPullRequest) `
    from https://github.com/flutter/packages/actions/runs/23563276945/job/68608396579 
    
    ## 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.
    hannah-hyj authored Mar 30, 2026
    Configuration menu
    Copy the full SHA
    b04f3e5 View commit details
    Browse the repository at this point in the history
Loading