-
Notifications
You must be signed in to change notification settings - Fork 26.7k
Flutter build release 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
(previously known asalpha
): The latest fully-tested build. Usually functional, but see Bad Builds for a list of known "bad" dev builds. -
beta
: Every few weeks, we pick the "best"dev
build of the previous month or so, and promote it tobeta
. These builds have been tested with our codelabs.
Eventually we will also have a release
build, which will be the best beta
build of the previous year or so, but we haven't yet reached a quality level that we are sufficiently happy with to use this label yet.
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.
Issue: When switching channels, you see an error message Unable to upgrade Flutter: no upstream repository configured.
Workaround: 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.
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.
- Home of the Wiki
- Roadmap
- API Reference (stable)
- API Reference (main)
- Glossary
- Contributor Guide
- Chat on Discord
- Design documents
- Code of Conduct
- Issue triage reports (latest)
- Our Values
- Tree hygiene
- Issue hygiene and Triage
- Style guide for Flutter repo
- Project teams
- Contributor access
- What should I work on?
- Popular issues
- Running and writing tests
- Release process
- Flutter Framework Gardener Rotation
- Rolling Dart
- Manual Engine Roll with Breaking Commits
- Updating Material Design Fonts & Icons
- Postmortems and Retrospectives
- Hotfix Documentation Best Practices
- In case of emergency
- Landing Changes With Autosubmit
- Setting up the Framework development environment
- The Framework architecture
- API Docs code block generation
- Running examples
- Using the Dart analyzer
- The flutter run variants
- Test coverage for package:flutter
- Writing a golden-file test for package:flutter
- Managing template image assets
- Setting up the Engine development environment
- Compiling the engine
- Debugging the engine
- Using Sanitizers with the Flutter Engine
- Testing the engine
- The Engine architecture
- Flutter's modes
- Crashes
- more...
- Setting up the Packages development environment
- Plugins and Packages repository structure
- Contributing to Plugins and Packages
- Understanding Packages tests
- Plugin Tests
- Releasing a Plugin or Package
- more...