-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Comparing changes
Open a pull request
base repository: flutter/packages
base: 582f0e714974
head repository: flutter/packages
compare: b04f3e5222a8
- 6 commits
- 29 files changed
- 5 contributors
Commits on Mar 30, 2026
-
[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.
Configuration menu - View commit details
-
Copy full SHA for f1cdf0b - Browse repository at this point
Copy the full SHA f1cdf0bView commit details -
[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.
Configuration menu - View commit details
-
Copy full SHA for 6aec00b - Browse repository at this point
Copy the full SHA 6aec00bView commit details -
[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.
Configuration menu - View commit details
-
Copy full SHA for 4f94ee2 - Browse repository at this point
Copy the full SHA 4f94ee2View commit details -
[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>
Configuration menu - View commit details
-
Copy full SHA for eab1265 - Browse repository at this point
Copy the full SHA eab1265View commit details -
[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.
Configuration menu - View commit details
-
Copy full SHA for 1de9829 - Browse repository at this point
Copy the full SHA 1de9829View commit details -
[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.
Configuration menu - View commit details
-
Copy full SHA for b04f3e5 - Browse repository at this point
Copy the full SHA b04f3e5View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 582f0e714974...b04f3e5222a8