[ci] Adds more ci checks for batch release file integrity#10859
[ci] Adds more ci checks for batch release file integrity#10859auto-submit[bot] merged 17 commits intoflutter:mainfrom
Conversation
32a0557 to
dcd190f
Compare
There was a problem hiding this comment.
Code Review
This pull request enhances the CI checks for batch release file integrity by adding validation for workflow files, triggers, and branches for packages that opt into batch releases. It also opts in the go_router package to this new system. The changes are well-tested and improve the reliability of the release process. I have a few suggestions to further improve the robustness of the new checks and clean up a minor code duplication issue in the tests.
|
reason for override, ci change that doesn't affect go_router functionality |
stuartmorgan-g
left a comment
There was a problem hiding this comment.
LGTM with minor changes, but per my comment on the docs PR I just realized we haven't fixed update-release-info yet. Since that's what we tell contributors to use, we shouldn't land this until that's been updated.
| @@ -0,0 +1,3 @@ | |||
| changelog: | | |||
| - Converts go_router to use batch release. | |||
There was a problem hiding this comment.
I thought the resolution of the comment thread was that this wasn't going to have a changelog entry?
There is no change in any part of the package that affects clients.
| } | ||
|
|
||
| final String content = workflowFile.readAsStringSync(); | ||
| YamlMap? yaml; |
875413e to
10fd358
Compare
10fd358 to
9c2244e
Compare
9c2244e to
60dfe25
Compare
| workflowDir | ||
| .childFile('release_from_branches.yml') | ||
| .writeAsStringSync('something'); | ||
| .writeAsStringSync('name: something'); |
There was a problem hiding this comment.
so that it won't trigger invalid yaml error which is not the focus of this test
|
autosubmit label was removed for flutter/packages/10859, because - The status or check suite Mac_arm64 ios_platform_tests_shard_3 master has failed. Please fix the issues identified (or deflake) before re-applying this label.
|
flutter/packages@1e50195...af1d610 2026-02-12 brunocorona.alcantar@gmail.com [video_player_avfoundation] Fix regression where http headers were ignored (flutter/packages#10991) 2026-02-12 47866232+chunhtai@users.noreply.github.com [ci] Adds more ci checks for batch release file integrity (flutter/packages#10859) 2026-02-12 stuartmorgan@google.com [google_maps_flutter] Create SDK 9 and 10 packages for iOS (flutter/packages#10852) 2026-02-12 katelovett@google.com Update codeowners (flutter/packages#11004) 2026-02-11 engine-flutter-autoroll@skia.org Roll Flutter (stable) from 67323de to 44a626f (1372 revisions) (flutter/packages#10999) 2026-02-11 stuartmorgan@google.com [video_player] Convert iOS unit tests to Swift (flutter/packages#10989) 2026-02-11 47866232+chunhtai@users.noreply.github.com [ci] updates `update-release-info` to support batch release (flutter/packages#10958) 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
also opts in go_router
Pre-Review Checklist
[shared_preferences]pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under1.CHANGELOG.mdto add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under1.///).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 ↩3