test: guard engines.vscode against Cursor's VS Code base#283
Merged
Conversation
Adds a unit test asserting the minimum required VS Code version stays compatible with the older base that Cursor ships, so a future bump that would break installation on Cursor is caught. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
mszabo-wikia
approved these changes
Jul 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Guards
engines.vscodeagainst being bumped past the older VS Code base that Cursor ships on, which would break installation there. Follow-up to #281.The minimum required version is asserted against a documented
CURSOR_VSCODE_BASEconstant; bump the constant only after confirming Cursor's base has moved forward.