Extensions are not updated to the latest versions

When I use Cursor, the latest extension I get for Biome (pre-release) is:

v2024.8.301002 (pre-release)

Yet, in VS Code, I get:

v2024.9.91939 (pre-release)

Even when manually trying to update extensions, I cannot get the latest versions.

Cursor:
Version: 0.40.4
VSCode Version: 1.91.1
Commit: 63dae81aea2c3fc079420fe72578a8eef26ba870
Date: 2024-09-05T02:52:05.660Z
Electron: 29.4.0
ElectronBuildId: undefined
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.6.0

VS Code:
Version: 1.92.2
Commit: fee1edb8d6d72a0ddff41e5f71a671c23ed924b9
Date: 2024-08-14T17:29:30.058Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.6.0

1 Like

I am also experiencing this issue. The Marimo extension is stuck on version 0.4.5 in Cursor despite being 0.4.8 on the VS Code marketplace.

Version: 0.42.5
VSCode Version: 1.93.1
Commit: 001668006cc714afd397f4ef0d52862f5a095530
Date: 2024-11-14T00:33:36.512Z
Electron: 30.4.0
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.1.0


(second post because “only 1 embedded media allowed per post”)

Hey, it looks like this has already been updated.

Could it be because Cursor is caching the extensions on their own infrastructure, and only updating them a bit later than the VS Code marketplace? Or is it because of the lower VS Code core version that is part of Cursor?

Because again, in VS Code I get Biome v2024.11.211321, and in Cursor the latest one is v2024.10.131712. That’s really annoying.

Same here, I get old version of an extension