[#178] Automate release process (2)

[pmeinhardt]

Check out np for releasing Tickety-Tick ✌️

⚠️ Note: The webpack GitRevisionPlugin is not outputting the correct COMMITHASH and VERSION yet, because the npm/yarn version script runs just before commiting.

[klappradla]

I think it makes sense to pick this up again for setting up the automation flow I roughly outlined in #178 (comment) @pmeinhardt. If we want to trigger build magic on CI based on pushing tags, utilizing yarn release and np could be a starting point.

Given we currently don't actually support Safari any more, I would probably already get rid of the extra parts for it.

[pmeinhardt]

Thanks a ton @klappradla for looking into release automation. 💚

I'd actually be fine with dropping Safari support. It simplifies a lot of things (webpack config, repo structure, preferences… reduces extra abstractions in app initialization/React context…).

Also, it seems like a new, compatible Safari version would essentially be a completely different code base with Apple deciding to go "native app extensions" rather sticking to the WebExtension standards. #210