Extension update visible but not installable due to engines

[SamVerschueren]

• VSCode Version: 1.5.3
• OS Version: macOS sierra

Steps to Reproduce:

1. Install the final-newline extension in VS Code 1.5.3 (this is important!)
2. It will install final-newline@0.2.0 because that one was target to 0.10.x
3. Enable the extension and search again for the final-newline extension in the extension list. It will show that their is an update available, namely 0.3.0, but that version is targetted to ^1.6.x
4. You can try to install the plugin, which looks like it succeeds, but when restarting VS Code, it will again show up as update.

Extension list should show 0.2.0 as 0.3.0 is not supported by VS Code 1.5.3

After installing the extension and enabling it, this is what shows up in the extension list

So it succesfully installs the correct version, only the notification shouldn't be showing.

FYI @joaomoreno

[SamVerschueren]

That also makes me wonder, is engines fully semver compatible? Because I used ^1.6.x which means that it won't work on 2.0.0 if it ever comes out. So I might be better using >=1.6 instead?

[joaomoreno]

#11573

Yes, it's the semver format.

[SamVerschueren]

Thanks @joaomoreno !