Flutter build release channels

Ian Hickson edited this page Oct 26, 2018 · 10 revisions

Flutter's channels

Flutter has the following channels, in increasing order of stability:

master

The current tip-of-tree, absolute latest cutting edge build. Usually functional, though sometimes we accidentally break things.

dev

The latest fully-tested build. Usually functional, but see Bad Builds for a list of known "bad" dev builds. We continually try to roll master to dev. Doing so involves running many more tests than those that we run during master development, which is why this is not actually the same to master.

beta

Every month, we pick the "best" dev build of the previous month or so, and promote it to beta. These builds have been tested with our codelabs.

stable

Eventually we will also have a stable build, which will be the best beta build of the previous quarter or so, but we haven't yet reached a quality level that we are sufficiently happy with to use this label yet.

How to change channels

You can see which channel you're on with the following command:

$ flutter channel
Flutter channels:
* beta
  dev
  master

To switch channels, run flutter channel [<channel-name>], and then run flutter upgrade to ensure you're on the latest.

Known issues and workarounds

When switching channels, you see an error message Unable to upgrade Flutter: no upstream repository configured.

You could get into this state if you ran flutter channel beta before the beta channel was officially released, due to a bug that has now been fixed. To resolve, run the following command from the root directory where Flutter is installed:

$ git fetch origin; git branch -u origin/beta beta; flutter channel beta 

After running this command, you should be back on the beta branch and be able to run flutter upgrade to complete the upgrade process.

After running flutter upgrade, the flutter tool crashed with a message about "Cannot find executable for /path/to/dart"

This will only happen when you first upgrade. The issue has since been fixed, and after the first time it happens, you won't see the crash again.

See also

  • Release process, which describes the details for how we push builds from channel to channel.
  • Changelog, where we describe changes since the last beta release.
Clone this wiki locally
You can’t perform that action at this time.
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.
Press h to open a hovercard with more details.