Create a v2 branch instead of moving the tag

[LitoMore]

Hi team, it looks like you force-pushed the v2 tag in the v2.0.1 release. We could create a v2 branch to avoid the force-push.

Let's say we're going to release the v2.0.2 version:

1. Remove the v2 tag,
2. Create a v2 branch to the latest release
3. Prepare the code, and update & commit everything to the main branch, including the package.json
4. Create a new release with the v2.0.2 tag
5. git switch v2 && git merge main && git push origin v2
6. Done

So that you don't have to move the v2 tag with force-push in every release.

For the v2.0.3 version, it becomes:

1. Prepare the code, and update & commit everything to the main branch, including the package.json
2. Create a new release with the v2.0.3 tag
3. git switch v2 && git merge main && git push origin v2
4. Done

You can use the same solution for v1 releases.

[xhyrom]

Sounds good, we can do it 👍