Skip to content

Verify that flutter upgrade could handle a "new" release with an older commit #170679

@matanlurey

Description

@matanlurey

This is a postmortem action item to help decide how we'd fix a "bad release" in the future.


Imagine that we had pushed the contents of 3.32.2 as 3.32.4 to (temporarily) fix the broken release, 3.32.3.

We are not sure if we had done this, if it would have worked.

We could try experimenting, i.e. with a beta release, or otherwise perhaps try to mock/stub this happening locally (i.e. it's just git).

@jtmcdole Did you want to try this? If not let's assign it to @bkonyi - I have too many AIs (#170547, #170561, #170568) on my plate at the moment to take this up.

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listinfra: releaseRelease-related requests and toolingteam-toolOwned by Flutter Tool team

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions