flutter 0.1.7

[koral--]

What to do if the build fails?

At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.

New Pull Request Checklist

Please mark the points which you did / accept.

• [x] I will not move an already shared step version's tag to another commit
• [x] I read the Step Development Guideline
• [x] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
• [x] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
• [x] I read and accept the Abandoned Step policy

[bitrise-coresteps-bot]

Don't forget to follow semantic versioning! Breaking changes (including step inputs) should be in major versions only.

step.yml changes compared to previous version:

--- steps/flutter/0.1.5/step.yml    2024-10-25 11:54:22
+++ steps/flutter/0.1.7/step.yml    2024-10-25 11:54:23
@@ -20,8 +20,8 @@
 source_code_url: https://github.com/DroidsOnRoids/bitrise-step-flutter
 support_url: https://github.com/DroidsOnRoids/bitrise-step-flutter/issues
-published_at: 2024-05-27T20:18:00.691717+02:00
+published_at: 2024-10-25T13:53:14.656674+02:00
 source:
   git: https://github.com/DroidsOnRoids/bitrise-step-flutter.git
-  commit: 4ddca8041dc822e52993ba90db916d6f83bf7b68
+  commit: add8cc531d26dcb7726cb2dfa5ba61bd97888fad
 host_os_tags:
 - osx-10.10