# Cursor rebase to VS Code MINOR versions (v1.95+)

**URL:** <https://forum.cursor.com/t/cursor-rebase-to-vs-code-minor-versions-v1-95/30588>\
**Category:** Feature Requests\
**Created:** [November 27, 2024, 10:54am UTC](https://forum.cursor.com/t/cursor-rebase-to-vs-code-minor-versions-v1-95/30588 "2024-11-27T10:54:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mjnowen](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mjnowen/32/7815_2.png) [@mjnowen](https://forum.cursor.com/u/mjnowen)\
**Post date:** [November 27, 2024, 10:54am UTC](https://forum.cursor.com/t/cursor-rebase-to-vs-code-minor-versions-v1-95/30588/1 "2024-11-27T10:54:29Z")

</div>

I have asked this a few times now. Can Cursor provide a more timely, scheduled (ie: reliable) timeline for regular rebasing to a newer version of VS Code. Cursor is generally always lagging 2+ versions behind and this causes issues with VS Code extension versions that might be locked behind a newer version of VS Code. Hence, I need Cursor to deliver timely rebasing.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [June 18, 2026, 10:20am UTC](https://forum.cursor.com/t/cursor-rebase-to-vs-code-minor-versions-v1-95/30588/2 "2026-06-18T10:20:29Z")

</div>

Closed on June 18, 2026, 10:20am UTC