You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
☂️ add github actions for flutter releases #139604
changed the title [-][flutter release] umbrella tracking bug to add github actions for flutter releases[/-][+]☂️ add github actions for flutter releases[/+]on Jan 3, 2024
01/18: will be more explicit on the latest update of this project (previously tracking through go/snippets)
landed #141652 yesterday which should address the token error.
Currently evaluating the effect of this PR but will need to wait for more data points (need more PRs that merge onto master branch and has a newer base commit than 6e39eb7. Current PRs as of right now have old bases)
Meanwhile, created #141819 to track the number of randomly picked PRs from master branch, that would hit a merge conflict when cherry picked to release branch.
01/22: Created #141980 to track failed to push issue from github actions.
Provided more details in the issue but several workarounds we have tried so far all failed. switching accounts and wait for candidates cause some delay in the testing process
01/24: tested 3 Pull requests on #142058 but they all have an older base. need to wait for more data points. meanwhile #137316 becomes the first PR that successfully triggers the workflow, but the workflow file could not be displayed in the run
This issue is assigned to @XilaiZhang but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
This issue was assigned to @XilaiZhang but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
[github actions] Automate Flutter Chery Picks (#139524)
[-][flutter release] umbrella tracking bug to add github actions for flutter releases[/-][+]☂️ add github actions for flutter releases[/+]XilaiZhang commentedon Jan 19, 2024
01/18: will be more explicit on the latest update of this project (previously tracking through go/snippets)
landed #141652 yesterday which should address the token error.
Currently evaluating the effect of this PR but will need to wait for more data points (need more PRs that merge onto master branch and has a newer base commit than 6e39eb7. Current PRs as of right now have old bases)
Meanwhile, created #141819 to track the number of randomly picked PRs from master branch, that would hit a merge conflict when cherry picked to release branch.
XilaiZhang commentedon Jan 22, 2024
01/22: Created #141980 to track failed to push issue from github actions.
Provided more details in the issue but several workarounds we have tried so far all failed. switching accounts and wait for candidates cause some delay in the testing process
XilaiZhang commentedon Jan 23, 2024
01/23: created #142058 to fix the #141980 the mysterious git push error
XilaiZhang commentedon Jan 24, 2024
01/24: tested 3 Pull requests on #142058 but they all have an older base. need to wait for more data points. meanwhile #137316 becomes the first PR that successfully triggers the workflow, but the workflow file could not be displayed in the run
XilaiZhang commentedon Jan 26, 2024
01/26: action to cherry pick pull request is ready now.
Did some tests on recent commits landed to flutter/flutter, and they look good. more details in #141819
The only constraint is that PR to be cherry picked must have a base commit that is AFTER #142058
4 remaining items
XilaiZhang commentedon Feb 7, 2024
02/07: cl/605120823 Change cherry pick request list to include both PR and issues
XilaiZhang commentedon Feb 23, 2024
02/23: #144065 to rewrite cherry pick template
XilaiZhang commentedon Mar 20, 2024
03/20: plans to collect feedbacks and conclude this project:
cc @godofredoc to check if the plan sounds good
XilaiZhang commentedon Mar 26, 2024
03/26: sent follow up email to collect feedbacks from iOS team on cherry pick actions.
XilaiZhang commentedon Apr 19, 2024
cherry pick action announcement was sent on 04/02
flutter-triage-bot commentedon May 15, 2024
This issue is assigned to @XilaiZhang but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
flutter-triage-bot commentedon Jun 26, 2024
This issue was assigned to @XilaiZhang but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.
matanlurey commentedon May 16, 2025
Closing as stale. Please feel free to open a new issue with a strong justification for doing this.
(To be clear, the
-releaseand-infrateams have no plans to work on this in the known future)github-actions commentedon May 30, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.