The vsce
tool on package or publish should be validating semver validity
#871
Milestone
vsce
tool on package or publish should be validating semver validity
#871
I know that microsoft/vsmarketplace#50 refers to the marketplace supporting full SemVer, but this issue is about ensuring that the toolchain used to package/publish match the expected Marketplace. Today you can have 'proper' semver in your versioning (1.0.2-beta.g893fd) and vsce will gladly package and attempt to publish. In fact there is a
semver.valid()
check (https://github.com/Microsoft/vscode-vsce/blob/main/src/validation.ts#L35) that does this. But knowing that the marketplace will not support this, it is giving false hopes that all the pipeline is valid until the very last step.Until/unless Marketplace supports full semver, then
vsce
should change to ensure that versions being used can actually get published. Today, it is not helping that validity.There are a few issues from 3-5 years ago on this, but the problem still remains...and regardless of the mismatch of support of the Marketplace, the
vsce
tool is incorrectly allowing a package and publish attempt all the way until the end knowing that it is NOT going to be successful. Thesemver.valid()
check should be modified to look for the unsupported semver aspects and block.The text was updated successfully, but these errors were encountered: