ci: restructured, cleaned, added pub.dev checks

[daadu]

• [deploy_demo]: proper step name, switched to "stable"
• [pr_title]: proper step name

[daadu]

@WieFel Will release v0.7.0 after this merge.

[daadu]

@WieFel Can you review now.

[WieFel]

@daadu what I find a bit strange is using .sh files for installing flutter + dependencies. Why did you come up with that solution, instead of using existing github actions that can be included?

[daadu]

@daadu what I find a bit strange is using .sh files for installing flutter + dependencies. Why did you come up with that solution, instead of using existing github actions that can be included?

Mainly to make the step faster - check new - 59s vs old - 66s, although the difference is not much, I expected more though!

[daadu]

I was expecting the 3rd party action to be using caching - for flutter binary - but looks like they don't. May be with our script can add caching to make it faster.

[WieFel]

@daadu what I find a bit strange is using .sh files for installing flutter + dependencies. Why did you come up with that solution, instead of using existing github actions that can be included?

Mainly to make the step faster - check new - 59s vs old - 66s, although the difference is not much, I expected more though!

In my opinion, readability/clarity of the actions would be more important in this case than 5s of quicker execution.
But of course, if you prefer it this way it is also fine with me ;) you have the final word.

[daadu]

In my opinion, readability/clarity of the actions would be more important in this case than 5s of quicker execution. But of course, if you prefer it this way it is also fine with me ;) you have the final word.

going with your suggestion. makes sense.

[daadu]

@WieFel The total difference on run is of 30s - current vs previous

[daadu]

We can try adding caching to current to reduce time or come back to git clone approach. Anyways not important for now, just for note - if in future the CI becomes slower - we might have to think on it.

[WieFel]

@daadu ok!
Yeah I think 30s difference is ok for now. Github actions are actually not trimmed for running very fast anyway. Their purpose is to run on some events and give feedback, regardless of needing few seconds more or less 😉

[daadu]

I think CI feedback should be fast though - like in about a 1-2m should know things are ok!

[WieFel]

Yeah sure! As long as it is within this limit it is ok