Closed
Description
There seems to be a new(?) issue with version checking with @types/vscode
and engines.vscode
.
In this first example, I have engines.vscode
set to ^1.46.0
and @types/vscode
set to 1.45.1
:
$ vsce package --yarn
ERROR @types/vscode 1.45.1 greater than engines.vscode ^1.46.0. Consider upgrade engines.vscode or use an older @types/vscode version
error Command failed with exit code 1.
In this example, I have engines.vscode
set to ^1.45.0
and @types/vscode
set to 1.45.1
:
$ vsce package --yarn
ERROR @types/vscode 1.45.1 greater than engines.vscode ^1.45.0. Consider upgrade engines.vscode or use an older @types/vscode version
error Command failed with exit code 1.
IMO, both should succeed. Also in at least the first case the message is wrong way around too.
Metadata
Metadata
Assignees
Type
Projects
Relationships
Development
No branches or pull requests
Activity
joaomoreno commentedon Jun 9, 2020
There is definitely an issue in the comparison code, since this is wrong:
But this seems right to me:
@eamodio Why do you say both should succeed?
@octref Can you explain what the semantics behind this are? It seems the first case is a bug. As for the second case... why wouldn't that work?
eamodio commentedon Jun 9, 2020
@joaomoreno yeah, you are right, the 2nd one should not succeed. I was just thinking that since
^1.45.0
is basically1.45.x
it felt like it should succeed, but agree that it shouldn't.joaomoreno commentedon Jun 10, 2020
Ah that makes it easier then! Let's fix 🔨