We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
===
>=
When the extension is installing the backing tool, the comparison should be === not >=; i.e., ensure exact version match.
The text was updated successfully, but these errors were encountered:
@brettfo : What is the impact of this? Would this only affect customers installing a private vsix in certain niche scenarios?
Sorry, something went wrong.
That's what initially led to the discovery of this, but it's also an issue if somebody rolls back their extension to a previous version.
Successfully merging a pull request may close this issue.
When the extension is installing the backing tool, the comparison should be
===
not>=
; i.e., ensure exact version match.The text was updated successfully, but these errors were encountered: