better use version instead of git tag for publishing generic package?

[manlao]

Current

generic package use git tag as package_version

Expected

according to gitlab docs, better use version instead?

[JonasSchubert]

Using semantic-release the git tag and package version should be the same. I didn't stumble upon anything different yet.
Do you have an use case where they differ?

[manlao]

Using semantic-release the git tag and package version should be the same. I didn't stumble upon anything different yet. Do you have an use case where they differ?

I tried to download a package file with release version number only (nextRelease.version) using gitlab package api, then found the package version is release version number with v (nextRelease.gitTag).

I think it's better to document it or be consistent with version number.

Thanks

[JonasSchubert]

@manlao thanks for the explanation and the catch.
I think you are correct. Also to be consistent with semantic-release/npm we should use the version instead of the git tag.
@fgreinacher what do you think? I would proceed and fix this.

[fgreinacher]

I agree, let’s go for consistency 👍

[JonasSchubert]

@manlao Thanks for pointing out the inconsistency. PR is created here.

[fgreinacher]

This has been fixed.