If you’ve typed `uses: subosito/flutter-action@v2` into a workflow file, you’ve already found the action almost every Flutter project on GitHub relies on to install the SDK on a runner. What trips people up isn’t finding it — it’s the details: which inputs actually exist, why `flutter-version: stable` throws an error, what the outputs are called, …
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Websites store cookies to enhance functionality and personalise your experience. You can manage your preferences, but blocking some cookies may impact site performance and services.
Essential cookies enable basic functions and are necessary for the proper function of the website.
These cookies are needed for adding comments on this website.
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
SourceBuster is used by WooCommerce for order attribution based on user source.
You can find more information in our Cookie Policy and Privacy Policy.