[ci] presubmit flags pending changelog with version promote on post 1… - #12435
Merged
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request adds validation to ensure that the 'promote' version change is only applied to pre-1.0 packages, along with corresponding unit tests. The feedback suggests simplifying the pubspec version retrieval by utilizing the already validated and cached version, thereby removing redundant parsing and null checks.
….dart Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
stuartmorgan-g
approved these changes
Aug 12, 2026
stuartmorgan-g
left a comment
stuartmorgan-g
left a comment
Collaborator
There was a problem hiding this comment.
LGTM, thanks for catching this!
chunhtai
added
the
autosubmit
pull Bot
pushed a commit
to Mattlk13/flutter
that referenced
this pull request
Aug 13, 2026
…r#191074) flutter/packages@94485f1...a3e763e 2026-08-13 engine-flutter-autoroll@skia.org Manual roll Flutter from 27b0988 to c243752 (179 revisions) (flutter/packages#12453) 2026-08-12 katelovett@google.com [material_ui] Undo relaxed constraints (flutter/packages#12451) 2026-08-12 fluttergithubbot@gmail.com Sync release-cupertino_ui-1.0.0 to main (flutter/packages#12450) 2026-08-12 fluttergithubbot@gmail.com Sync release-material_ui-1.0.0 to main (flutter/packages#12448) 2026-08-12 happytoday83@naver.com [camera_android_camerax] Fix leaked thread per capture in `takePicture` (flutter/packages#12361) 2026-08-12 jmccandless@google.com [material_ui, cupertino_ui] Prepare to release 1.0.0 (flutter/packages#12425) 2026-08-12 jmccandless@google.com [material_ui, cupertino_ui] READMEs (flutter/packages#12428) 2026-08-12 47866232+chunhtai@users.noreply.github.com [ci] presubmit flags pending changelog with version promote on post 1… (flutter/packages#12435) 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-flutter-autoroll Please CC flutter-ecosystem@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: 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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
….0.0
as title
Pre-Review Checklist
[shared_preferences]///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot 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.Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2