Tag creation vs Release about releaser-tools HOT 2 OPEN

I hit this hard because when I have seen this :

Recommended workflow

1. Make changes
2. Commit those changes
3. Make sure GitLab CI turns green
4. Bump version in package.json
5. Commit package.json files
6. Tag
7. Push
8. conventionalGitlabReleaser

Sounds really what I needed but for doing this workflow you need to tag for building the release in CI then publish my release in Gitlab with built assets.

from releaser-tools.

Got into the same thing.
I was looking on the recommended workflow but the releaser won't work if a tag already exists on the source repo.

Also discovered (after some confusion) that there is a recommended gist on the conventional-gitlab-releaser README that does exactly that, creates a tag with npm publish then pushes tags.

I realized it was fine, because the gist uses "conventional-github-releaser" (on line 27).
So the GitLab version method works different compared to the GitHub one.

Maybe instead of using

POST /projects/:id/repository/tags

we could use the releases API instead to create it

POST /projects/:id/releases

like the GitHub version repos/${context.owner}/${context.repository}/releases

from releaser-tools.