Approaches to dealing with canary/nightly releases

[kasperisager]

I've spent the past couple of days looking into how to one might approach canary/nightly releases using Berry and GitHub Actions. Something I can't quite seem to work out is how to ensure that prereleases can happen in a fully autonomous manner. At first, yarn version prerelease seemed like it would fit the bill perfectly. However, to ensure that it could operate autonomously, the release workflow would need to push the version increment back to the main branch to avoid a version collision the next time a prerelease is made. The bad news is that this isn't currently possible as we use protected branches: https://gh.neting.ccmunity/t/allowing-github-actions-bot-to-push-to-protected-branch/16536

My next thought was to instead use a timestamp as a version postfix, but there doesn't yet seem to be a good way to do this with the version plugin. The only option I found was passing the full version to yarn version which isn't easy to automate. Either way, this would solve the issue of having to push the version increment back to the main branch as we could just discard it and be sure that the next prerelease wouldn't cause a version collision.