Skip to content

Keeping track of flutter version for projects and downgrading flutter / dependencies #6000

@danafergan

Description

@danafergan

I've been working on an experimental project with collaborators using older versions of flutter. Since their source code is reliant on older versions of flutter and I have a current version, I spent a lot of time debugging and finding out why certain syntax wouldn't work on my machine (i.e. the change from window -> physicalWindow) and why we had different output from the same code.

I also couldn't find a good way to downgrade flutter because simply checking out an older version doesn't change the version (at least according to flutter doctor) and I couldn't downgrade all of the flutter dependencies.

What is the best practice for managing flutter version in a project, and is there a good way to change versions?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions