Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
The revision on trunk to cherrypick.
Once applied, the actual commit revision of the cherrypick.
Used in:
The cherrypick has not yet been applied.
The cherrypick has not been applied and will require manual resolution.
The cherrypick has been successfully applied to the local checkout. This state requires Cherrypick.appliedRevision to also be set.
The cherrypick will NOT be applied in this release.
One of 'stable', 'beta', or 'dev'
The name of the release.
The current [ReleasePhase] that has yet to be completed.
A string used to validate that the current conductor is the same version that created the [ConductorState] object.
Used in:
Git tag applied to framework RC branch HEAD and pushed upstream.
Package artifacts verified to exist on cloud storage.
There is no further work to be done.
The type of release that is being created. This determines how the version will be calculated.
Used in:
All pre-release metadata from previous beta releases will be discarded. The z must be 0.
Increment z.
Compute x, y, and m from the candidate branch name. z and n should be 0.
Increment n.
A git remote
Used in:
Used in:
The development git branch the release is based on. Must be of the form /flutter-(\d+)\.(\d+)-candidate\.(\d+)/
The commit hash at the tip of the branch before cherrypicks were applied.
The difference in commits between this and [startingGitHead] is the number of cherrypicks that have been currently applied.
Path to the git checkout on local disk.
The remote commits will be fetched from.
The remote cherrypicks will be pushed to create a Pull Request. This should be a mirror owned by the user conducting the release.
Desired cherrypicks.
For the repository that has a dart_revision in a DEPS file.
Name of local and remote branch for applying cherrypicks. When the pull request is merged, all commits here will be squashed to a single commit on the [candidateBranch].