Add a flutter update-packages --force-upgrade auto-roller

[jmagman]

Use case

Add an auto-roller to periodically merge the results of a flutter update-packages --force-upgrade if no tests fail.

[jmagman]

This has been mentioned a few times in a few chats, but I couldn't find an issue for it.

[jmagman]

Right now this is done manually: #37971

[Hixie]

keywords: autoroller update packages force upgrade

[Hixie]

@godofredoc this would be a really useful bot, fwiw.

[Hixie]

cc @dnfield since he's worked on some of our bots

[dnfield]

@rmistry could this be a good candidate to fit in with what the Skia autorollers do?

We could write a custom bot to do this in Dart, but if there's already functionality to do it in the Skia autorollers that would be nice.

Effectively, we'd have to:

clone the repo
run flutter update-packages --force-upgrade
Commit the result of that
Open a PR with it.
cc or notify someone if it fails (it frequently can fail if, for example, a package we try to upgrade has a breaking change in it).

[zanderso]

There are some examples of using github actions to accomplish what we want: https://github.com/peter-evans/create-pull-request/blob/master/docs/examples.md#use-case-create-a-pull-request-to-update-x-periodically. Thoughts about this approach?

[zanderso]

/cc @jonahwilliams who I was just discussing this with.

[godofredoc]

There are several restrictions on using github actions, we may need to validate with security before implementing.

[jmagman]

There's also dependabot, if pub support gets implemented. dependabot/dependabot-core#2166

[godofredoc]

@christopherfujino I believe you already implemented this, can we close this bug?

[christopherfujino]

@christopherfujino I believe you already implemented this, can we close this bug?

Ahh thanks, didn't know about this! Closing as superceded by https://github.com/flutter/flutter/issues?q=is%3Aissue+is%3Aopen+autoroll+pub

[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.