Use the main yaru_widgets branch for software store development.

[whiskeyPeak]

I think this would make bugs in the yaru_widgets package a lot easier to fix and quicker to find. There should still be normal releases for both pieces of software for a "stable" experience, I just think it makes development a bit more precise and allows us to find regressions quicker if we're working on both main branches at the same time.

Instead of specifying a specific commit in pubspec.yaml, main can be added next to the ref.

WDYT?

[Feichtmeier]

I think using the main branch is a bit risky. The plan is to release yaru widgets 2.0.0 soon. So let's keep it pinned with a commit we know that works until the release is out

[jpnurmi]

Based on the lessons learned from other projects, I'd highly recommend using hosted releases or pinned SHA1s when using stuff straight from Git. Following main tends to turn the CI red in an uncontrollable manner and makes bisecting the history unnecessarily painful. There are great automated solutions such as Renovate and Dependabot for keeping dependencies up-to-date. These let you tackle breaking updates in a much nicer way. 😉