Another workaround: go to https://marketplace.visualstudio.com/items?itemName=betterthantomorrow.calva and click to download 2.0.269, save the .vsix file somewhere, then open Extensions and install from that VSIX...

(that's what I just did)

It'll be interesting if the VS Code team will have a closer look at this. And also if it will happen again with 270, or if there's something super-crazy-special about going from 268-269.

They are on it. They think it is a marketplace bug: https://github.com/microsoft/vsmarketplace/issues/384

Still only seeing 2.0.268 as latest in VS Code.

But, glad they are looking into it.

Even if you do check for extension updates?

Oh, I didn’t try that earlier, but now I noticed VS Code has seen the latest version (.269).

In the past I've had this issue with extensions, and typically went away after a few days, we just assumed it was an expected caching issue or something, but good to know that we can expect higher from vscode team and they're looking into it!

You mean by ”this issue” that you have seen a clean install pick latest without problems, while the updater can't see that version? I have never seen something like it before.

More reports of this problem: https://github.com/microsoft/vsmarketplace/issues/383

From the vscode marketplace team: > The team is still working to fix the issue, it's our only priority right now.

Oh damn nvm i definitely misinterpreted the problem