[#178] Automate release process (2)

bitcrowd / tickety-tick

A browser extension that helps you name branches and write better commit messages

MIT License

57 stars 10 forks source link

[#178] Automate release process (2) #184

Closed pmeinhardt closed 4 years ago

pmeinhardt commented 5 years ago

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 commented 4 years ago

I think it makes sense to pick this up again for setting up the automation flow I roughly outlined in https://github.com/bitcrowd/tickety-tick/issues/178#issuecomment-624559141 @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 commented 4 years ago

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. https://github.com/bitcrowd/tickety-tick/issues/210