Skip to content

☂️ add github actions for flutter releases #139604

Closed as not planned
Closed as not planned

Description

@XilaiZhang
  1. Use Github Actions to create flutter cherrypick functionality through github labels

  2. Use Github Actions to create engine->framework roll functionality

  3. Use Github Actions to create dart->engine roll functionality

  4. Use GitHub actions to update flutter licenses in release PRs

Activity

  1. self-assigned this
    on Dec 5, 2023
  2. added
    in triagePresently being triaged by the triage team
    and removed
    in triagePresently being triaged by the triage team
    on Dec 6, 2023
  3. 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
  4. XilaiZhang commented on Jan 19, 2024

    @XilaiZhang
    ContributorAuthor

    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.

  5. XilaiZhang commented on Jan 22, 2024

    @XilaiZhang
    ContributorAuthor

    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

  6. XilaiZhang commented on Jan 23, 2024

    @XilaiZhang
    ContributorAuthor

    01/23: created #142058 to fix the #141980 the mysterious git push error

  7. XilaiZhang commented on Jan 24, 2024

    @XilaiZhang
    ContributorAuthor

    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

  8. XilaiZhang commented on Jan 26, 2024

    @XilaiZhang
    ContributorAuthor

    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

  9. 4 remaining items

  10. XilaiZhang commented on Feb 7, 2024

    @XilaiZhang
    ContributorAuthor

    02/07: cl/605120823 Change cherry pick request list to include both PR and issues

  11. XilaiZhang commented on Feb 23, 2024

    @XilaiZhang
    ContributorAuthor

    02/23: #144065 to rewrite cherry pick template

  12. XilaiZhang commented on Mar 20, 2024

    @XilaiZhang
    ContributorAuthor

    03/20: plans to collect feedbacks and conclude this project:

    1. Collect feedbacks from members of the iOS team(e.g. Victoria, Jenn etc.), since we initially informed only the iOS team through email.
    2. Advertise the feature to more members of the Flutter team (e.g. engine team?)
    3. Apply fixes based on feedbacks from team members.
    4. Announce it to the entire flutter team.

    cc @godofredoc to check if the plan sounds good

  13. XilaiZhang commented on Mar 26, 2024

    @XilaiZhang
    ContributorAuthor

    03/26: sent follow up email to collect feedbacks from iOS team on cherry pick actions.

  14. XilaiZhang commented on Apr 19, 2024

    @XilaiZhang
    ContributorAuthor

    cherry pick action announcement was sent on 04/02

  15. flutter-triage-bot commented on May 15, 2024

    @flutter-triage-bot

    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!

  16. added
    ⏳Bot is counting down the days until it unassigns the issue
    on May 15, 2024
  17. flutter-triage-bot commented on Jun 26, 2024

    @flutter-triage-bot

    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.

  18. removed
    ⏳Bot is counting down the days until it unassigns the issue
    on Jun 26, 2024
  19. matanlurey commented on May 16, 2025

    @matanlurey
    Contributor

    Closing as stale. Please feel free to open a new issue with a strong justification for doing this.

    (To be clear, the -release and -infra teams have no plans to work on this in the known future)

  20. github-actions commented on May 30, 2025

    @github-actions

    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.

  21. locked as resolved and limited conversation to collaborators on May 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work list

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions