The upcoming version of my app needs a newer Flutter version than the previous release. I wonder how to edit the build metadata in a way that doesn’t cause a failed build.
If I just wait for the new release to be detected, the build will fail or - even worse - succeed and publish an artifact that is built with the old flutter version and is therefore likely broken.
If I add the release manually in advance, the build will fail until I actually create the release tag.
What’s the correct workflow here?
Set flutter as a submodule in your repo
USE that submodule in your actual CI so you never forget to update it
Tag as usual
…like this, there’s no need for you to edit anything in the recipe, just code as usual 
1 Like
Sounds good! Can you point me to some project that does this already?
1 Like
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.