Add tag/release on publishing

[janpio]

When a new version is released, the commit should be tagged so we can understand what exactly got released and the releases are listed in the "Releases" tab.

[divyenduz]

What to we want to name the tag?
What content do we want the tag message to have?
Do we need a release linked to a tag or just an annotated tag (which is also rendered by Github release page), example,

Started a WIP PR here #120

[janpio]

tag name = version name
tag message = tags do not have a message

[divyenduz]

tag name = version name

Do we want to tag both stable and unstable channel? If we just tag stable, we can use the version number yes.

tag message = tags do not have a message

Tags do have a message https://git-scm.com/book/en/v2/Git-Basics-Tagging

It rendered like this (https://github.com/prisma/vscode/releases/tag/0.0.30)

[janpio]

Do we want to tag both stable and unstable channel? If we just tag stable, we can use the version number yes.

No, we need to tag all the commits properly to make it obvious as what version it got released.

Annotated tags do have a message https://git-scm.com/book/en/v2/Git-Basics-Tagging

We are not super interested in that as we do not have anything to show there.
In theory we could add a link to the VSCode Marketplace there.

[janpio]

If we just tag stable, we can use the version number yes.

That limitation is a problem we need to fix then - add a prefix for example.

[divyenduz]

So, in my PR, I did the following:

Stable

Extension version: 0.0.33
Tag: v0.0.33

Unstable

Extension version: 0.0.7
Tag: v0.0.7-dev

And in the message I include the linked Prisma version.

[divyenduz]

We are not super interested in that as we do not have anything to show there.
In theory we could add a link to the VSCode Marketplace there.

Prisma version maybe?
I don't think Marketplace link can be tied to a version but we can add the link to the extension in the marketplace in general.

However, for older releases it might be misleading.

[divyenduz]

Can you please also answer the third question from here #73 (comment)

I think you missed it because I edited the comment as you were typing.

[divyenduz]

I marked the PR ready for review.

[janpio]

Do we need a release linked to a tag or just an annotated tag (which is also rendered by Github release page), example,

I would say that for the stable releases, we want a release where we can write release notes after release.