[ci] Adds repo checks in main branch for batch release#10485
Merged
auto-submit[bot] merged 3 commits intoflutter:mainfrom Jan 5, 2026
Merged
[ci] Adds repo checks in main branch for batch release#10485auto-submit[bot] merged 3 commits intoflutter:mainfrom
auto-submit[bot] merged 3 commits intoflutter:mainfrom
Conversation
50bdfb2 to
98b36da
Compare
chunhtai
commented
Nov 21, 2025
| } | ||
| } | ||
| } else { | ||
| switch (versionState) { |
Contributor
Author
There was a problem hiding this comment.
no change to this part, just put the original code into the else case
| expect( | ||
| output, | ||
| containsAll(<Matcher>[ | ||
| contains(' Checking ci_config.yaml...'), |
Contributor
Author
There was a problem hiding this comment.
Removed additional print to be more in sync with all the check in repo_package_info
47627d5 to
dd032aa
Compare
stuartmorgan-g
requested changes
Dec 3, 2025
82cfcd6 to
2285870
Compare
chunhtai
commented
Dec 5, 2025
| @@ -1,6 +0,0 @@ | |||
| # Use this file as template to draft a unreleased changelog file. | |||
Contributor
Author
There was a problem hiding this comment.
I have to delete this file because now the ci will check whether batch release is enabled if these file exists
33a042d to
fb0209c
Compare
Contributor
Author
|
change since last review is in the second commit |
1365946 to
2b68de2
Compare
stuartmorgan-g
requested changes
Dec 9, 2025
| /// | ||
| /// During a release (specifically the `update-changelogs` command), all | ||
| /// pending entries are aggregated, the package version is updated based on the | ||
| /// highest priority change, and `CHANGELOG.md` is updated. |
2b68de2 to
249a5ec
Compare
11 tasks
249a5ec to
659d47b
Compare
659d47b to
8ed96a8
Compare
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/flutter
that referenced
this pull request
Jan 6, 2026
github-merge-queue bot
pushed a commit
to flutter/flutter
that referenced
this pull request
Jan 6, 2026
flutter/packages@12eb764...d3f860d 2026-01-05 [email protected] [ci] Adds repo checks in main branch for batch release (flutter/packages#10485) 2026-01-05 [email protected] [ci] Pins github action commit hash (flutter/packages#10599) 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 [email protected] 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
ivan-vanyusho
pushed a commit
to ivan-vanyusho/packages
that referenced
this pull request
Jan 26, 2026
This fixes main branch part of flutter/flutter#176433 The work left is adjusting cocoon to also run this check in release branch The high level view of this pr. 1. Move ci_config.yaml and pending changelog parsing into thir own files and the parsed results are exposed as a getter method in RepositoryPackage so that it can be shared between branch_for_release, repo_package_info_check, and version_check 2. The format error of ci_config.yaml and changelog files are reported in repo_package_info_check. The other 2 assume they are correct formatted and throw directly if they are not. 3. update the version_check to be able to handle batch release package ## 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.
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
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.
This fixes main branch part of flutter/flutter#176433
The work left is adjusting cocoon to also run this check in release branch
The high level view of this pr.
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