Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Non-Semver Engine Versions in VSCE Validation and Comparison #1077

Open
mohankumarelec opened this issue Nov 9, 2024 · 0 comments · May be fixed by #1078
Open

Support Non-Semver Engine Versions in VSCE Validation and Comparison #1077

mohankumarelec opened this issue Nov 9, 2024 · 0 comments · May be fixed by #1078
Labels
feature-request Request for new features or functionality
Milestone

Comments

@mohankumarelec
Copy link

The Regex used for checking valid engine version, can have values like 1.96.x, which is not a valid semver.
When using these kinds of version, the semver version comparison fails.

if (!/^\*$|^(\^|>=)?((\d+)|x)\.((\d+)|x)\.((\d+)|x)(\-.*)?$/.test(version)) {
throw new Error(`Invalid vscode engine compatibility version '${version}'`);
}

if (engineVersion !== 'latest' && !semver.satisfies(engineVersion, '>=1.61', { includePrerelease: true })) {

@mohankumarelec mohankumarelec linked a pull request Nov 9, 2024 that will close this issue
@benibenj benibenj added the feature-request Request for new features or functionality label Nov 25, 2024
@benibenj benibenj added this to the January 2025 milestone Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants