Setup CI

[meandavejustice]

• add release template
  • https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#configuring-automatically-generated-release-notes
  • https://github.com/ipfs/ipfs-companion/releases/tag/v2.19.1
• setup github action to upload new builds to chrome web store (and eventually amo)
  • https://github.com/ReeganExE/quickpic/blob/c7c7b56ea5f1330f266755e83fcd2631c21d0dcb/.github/workflows/extension.yml

[meandavejustice]

extension build, bundle upload and publish to chrome web store is now working

[meandavejustice]

This is almost ready to be closed. I updated the out of date refresh token for chrome. Not sure why it expired so early, need to either update the refresh refresh token script, or figure out why it wrote me such an early expiring one. Things I've read point to having a release in "testing" in the store but I'm not seeing that in the UI. Once I get that figured out and verify once again that edge uploads are publishing correctly, I can close.

[meandavejustice]

Release will come after #43 is addressed this week

[meandavejustice]

#43 was addressed, as well as a bunch of other things. In order to close this out I would like to add this action https://github.com/butlerlogic/action-autotag to automatically tag a release when version is updated in package.json