Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide an easy way to select the version of Flutter to use #14230

Closed
rock3r opened this issue Jan 23, 2018 · 7 comments

Comments

@rock3r
Copy link
Contributor

commented Jan 23, 2018

This ties in with #14229 — it would be great if there was a way to select the version of Flutter to use from the flutter tool. Currently to my understanding the manual process to do so is:

$ cd flutter
$ git checkout [branch, tag or commit hash]
$ cd ../my-app/
$ flutter packages get

(assuming both the flutter folder and the my-app folder live in the same directory)

What would be nice would be able to use a command like flutter switch-to [version] (e.g., flutter switch-to 0.0.20). Ideally running flutter run or flutter build could do this automatically, but that poses the question of how it would work for people working on multiple projects using different versions of Flutter at the same time.

@rock3r

This comment has been minimized.

Copy link
Contributor Author

commented Jan 23, 2018

@Hixie

This comment has been minimized.

Copy link
Contributor

commented Jan 25, 2018

We have flutter channel <branch>, where branch is master, dev, or beta. We don't have a way to explicitly pick an old version. The problem with supporting that is that you're likely to switch to a version that doesn't support that command, and then you can't get back. So instead we encourage people to use "git checkout" (as above) if they want a very specific version.

@rock3r

This comment has been minimized.

Copy link
Contributor Author

commented Jan 25, 2018

I see your point; on the other hand, the sooner this is implemented the lesser that risk is. And I imagine once Flutter goes to a more "stable" setting such as betas or RCs or 1.x, it would become increasingly important to be able to easily enforce (and switch to) the version of Flutter a project was built with. I'm thinking more long-term than shorter term. You could easily put a lower bound on the version the command can downgrade too, as a safety net.

@Hixie

This comment has been minimized.

Copy link
Contributor

commented Jan 25, 2018

Yeah, having a lower bound would make sense for this.

@RafaO

This comment has been minimized.

Copy link

commented Dec 9, 2018

I think this is a good idea, or at least specify the version of flutter SDK that should be used. I see also a nice benefit here for shared projects where we need to make sure everyone uses the same flutter version.

@rrousselGit

This comment has been minimized.

Copy link
Contributor

commented May 18, 2019

This can probably be closed now that we can do flutter version v1.2.3

@DanTup

This comment has been minimized.

Copy link
Member

commented May 20, 2019

Yep, this was implemented in #26840. Thanks!

@DanTup DanTup closed this May 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.