Rollback Exercise: Publish and rollback 3.36 beta [after 3.35 stable]

[matanlurey]

As part of validating improvements after the Flutter 3.32.3 Postmortem, we will be publishing an intentionally "broken"¹ Flutter beta release (i.e. a hypothetical 3.36.0-0.3.pre), and then to "fix" it, publish an existing ("good") release (i.e. 3.36.0-0.4.pre) as a newer release (i.e. 3.36.0-0.5.pre).

All of the version numbers used above are for illustrative purposes only.

We're roughly targeting August 14 2025, or after the 3.35 stable is released.

---

Checklist:

• 3.35 stable is released
• Announce, via flutter-announce@, that we will be conducting this exercise, link to this issue
• Announce, via Discord, the same
• Add a cherrypick to flutter-3.36-candidate.0 that adds a silly message to flutter --version
• Publish the above to the beta channel
• Publish HEAD~1 (an older commit, before the cherrypick) to the beta channel to "fix" the issue
• Announce (same channels) the experiment has concluded, hopefully successfully

Footnotes

1. It will just print a silly message when you do flutter --version or something similar ↩

[matanlurey]

It looks like this experiment failed.

While the new build was published to the beta channel, it did not trigger the packaging builders.

[matanlurey]

Follow-up: #174717.