[ci] use override: post-release-<package> label#11429
Merged
auto-submit[bot] merged 1 commit intoflutter:mainfrom Apr 6, 2026
Merged
[ci] use override: post-release-<package> label#11429auto-submit[bot] merged 1 commit intoflutter:mainfrom
auto-submit[bot] merged 1 commit intoflutter:mainfrom
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the version check command to use the label prefix "override: " for post-release checks. Specifically, it modifies the label detection logic in version_check_command.dart and updates the corresponding test cases and descriptions in version_check_command_test.dart. I have no feedback to provide.
stuartmorgan-g
approved these changes
Apr 6, 2026
chunhtai
added
the
autosubmit
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/flutter
that referenced
this pull request
Apr 7, 2026
github-merge-queue bot
pushed a commit
to flutter/flutter
that referenced
this pull request
Apr 8, 2026
flutter/packages@5299279...0e0a032 2026-04-07 stuartmorgan@google.com [various] Ignore generated plugin files (flutter/packages#11455) 2026-04-06 engine-flutter-autoroll@skia.org Roll Flutter from 7245c3f to 9cd60b5 (30 revisions) (flutter/packages#11452) 2026-04-06 47866232+chunhtai@users.noreply.github.com [go_router] Manually Sync go_router release to main (flutter/packages#11449) 2026-04-06 10687576+bparrishMines@users.noreply.github.com [path_provider_android] Changes internal implementation to use JNI (flutter/packages#9770) 2026-04-06 47866232+chunhtai@users.noreply.github.com [ci] use override: post-release-<package> label (flutter/packages#11429) 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.
The ci only capture label that starts with
override:. We can either (1) update the ci to capture more labels, or (2) update the post release label to start withoverride:.I figured adding
override:prefix is more appropriate because the label is attempting to override verision check for batch release.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