You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed an interesting behavior when I use the flutter-version parameter passing a specific version.
As suggested in the documentation, if I try to use cache as cache-path: "${{ runner.tool_cache }}/flutter/:channel:-:version:-:arch :", version always returns the latest version of flutter, ignoring the value passed in flutter-version.
Is this behavior correct?
Wouldn't it make more sense if, when I pass the flutter-version: 3.19 parameter, for example, the version parameter receives flutter-version and not the latest version of flutter?
The text was updated successfully, but these errors were encountered:
I noticed an interesting behavior when I use the flutter-version parameter passing a specific version.
As suggested in the documentation, if I try to use cache as cache-path: "${{ runner.tool_cache }}/flutter/:channel:-:version:-:arch :", version always returns the latest version of flutter, ignoring the value passed in flutter-version.
Is this behavior correct?
Wouldn't it make more sense if, when I pass the flutter-version: 3.19 parameter, for example, the version parameter receives flutter-version and not the latest version of flutter?
The text was updated successfully, but these errors were encountered: