-
Notifications
You must be signed in to change notification settings - Fork 29.4k
Closed
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listinfra: releaseRelease-related requests and toolingRelease-related requests and toolingteam-infraOwned by Infrastructure teamOwned by Infrastructure teamtriaged-infraTriaged by Infrastructure teamTriaged by Infrastructure team
Description
See go/flutter-release-workflow#push.
| Argument | Value |
|---|---|
git_branch |
flutter-3.33.0-candidate.0 |
release_channel |
beta |
tag |
3.33.0-0.1.pre |
force |
true |
The branch appears to be close to a pushable state:
- 🚫
//bin/internal/engine.versionis out of date and needs to be set to f43bd5c. - ✅
//bin/internal/release-candidate-branch.versionis set as expected
The last engine build timed out due to racing resources with 3.32, so to fix that:
- Wait until after 3.32 is published so we don't fight over release resources
- Update
//bin/internal/engine.versionwith f43bd5c, submit PR. - Wait until
Linux flutter_release_builderis done building (~90 minutes) - Navigate to the dashboard for the branch
- Click the landed commit and hit
Run all tasksto trigger postsubmit tests: - After all of these steps are green, you can now follow go/flutter-release-workflow#push.
Note that @reidbaker and @matanlurey are likely to be unavailable, so for questions/escalations:
Metadata
Metadata
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listinfra: releaseRelease-related requests and toolingRelease-related requests and toolingteam-infraOwned by Infrastructure teamOwned by Infrastructure teamtriaged-infraTriaged by Infrastructure teamTriaged by Infrastructure team