tree: d963288622c03c8d2015779192635f3c547fa109 [path history] [tgz]
  1. build.yaml
  2. close-inactive-issues.yaml
  3. daily-dev-bump.yaml
  4. dcm-label.yaml
  5. dcm.yaml
  6. flutter-candidate-update.yaml
  7. flutter-prep.yaml
  9. release-notes.yaml
  10. scorecards-analysis.yml
  11. workflow-bot-cleanup.yaml



This job handles caching the flutter candidate, so that we don't need to keep downloading it and setting it up for each job.

Clearing the cache

To clear the Github Actions cache for a specific flutter candidate:

  • Navigate to Devtool's Actions Caches
  • Filter for the candidate you would like to clear
  • Delete all of the cache entries for your candidate
    • There should be a Linux and a MacOS entry for each candidate


The Daily Dev Bump workflow is meant to facilitate -dev.* version bumps, on a daily cadence.

Using a cron trigger, this workflow will:

  • perform a dev version bump

  • create a PR with an autosubmit label

  • The PR will then be automatically approved and merged by the processes from the Flutter Cocoon repo ,

    • The Flutter auto-submit bot automatically merges the PR.


In order to allow the automatic approval and submission of the version bump PRs, DartDevtoolWorkflowBot was created.

DartDevtoolWorkflowBot is a Github account that is used to author the version bump PRs in daily-dev-bump.yaml. It has special permissions so that when the Cocoon bots see a PR authored by DartDevtoolWorkflowBot, they can be automatically approved.

DartDevtoolWorkflowBot Token Cycling

DartDevtoolWorkflowBot's Personal Access Token must be cycled every 90 days. The instructions to rotate the token can be found in the email for the Dart DevTool Workflow Token rotation.

Manually Performing a Dev Version Bump

To manually trigger a Dev Version Bump: