automate release

[yzwdroid]

Issue This PR Addresses

Type of Change

• Bugfix: Change which fixes an issue
• New Feature: Change which adds functionality
• Documentation Update: Change which improves documentation
• UI: Change which improves UI

Description

Automate the release process by github action. To release a new version, we just add a tag when we push or merge a pr.

• only the commits follow the pattern will be added to the release note.
  https://github.com/lob/generate-changelog#usage

type(category): description [flags]

Where type is one of the following:

    breaking
    build
    ci
    chore
    docs
    feat
    fix
    other
    perf
    refactor
    revert
    style
    test

Checklist

• Quality: This PR builds and passes our npm test and works locally
• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
• Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

[yzwdroid]

I didn't update the release document yet, if this is the right method, I will update the document then.

[birtony]

This PR should be closed when #1628 is merged

[manekenpix]

Is it needed now? I think we can just close it? @humphd @birtony

[birtony]

Is it needed now? I think we can just close it? @humphd @birtony

I was thinking of waiting until #1628 is merged @manekenpix

[birtony]

Addressed in #1628. Closing.