Enable publish the developing branch to NPM with DevOps

[huan]

trafficstars

Currently, we are using a new branch dev without DevOps enabled.

I'd like to enable DevOps to each version that passed the CI to NPM. Here are two solutions:

1. We can start working on the main branch instead of dev, because we will publish to @next when the minor version is odd
2. We can add a GitHub Action to the dev branch, and publish this branch as [email protected].

I will prefer option 1: use the main branch with the @next version tag because it's most straightforward and easy to configure and is the most convenient way for the users including myself.

@wechaty/juzi Please let me know which one you prefer and let's enable the DevOps this month so that we can have a better pipeline in future developments.

Thank you very much.

[windmemory]

Currently we are working on a version that can be seamlessly integrated with our product. We will merge it to main after we finishes a full test with that version. And then let's use main as the working branch later.

[huan]

Ok, great to know that we will use main branch in our future works.

Looking forward to publishing the new version as @next soon!