Question for you @randy3k:
Throughout the work on 3.0.0, I must confess that I hadn't really noticed that the extension requires VS Code 1.110 or later.
Unfortunately, this is now blocking me at work. We run OpenVSCode Server (not my preferred choice, but a bigger engineering challenge than I'm able to fight rn), and the newest version available to us is 1.103.1. Changing platforms isn't a realistic option in the short term, so I'm stuck on vscode-R 2.8.x :'-(
AFAICT, this requirement came in with the session watcher rewrite in 4e1ca8b (#1684). I couldn't find a stated reason for the bump in the commit, the PR or the changelog. At the same time, I don't think that vscode-R 3.0.0+ actually uses any API newer than 1.75? I asked Claude to investigate and it agreed, pointing out that @types/vscode is still pinned at ^1.75.0, so any newer API would fail to type-check.
Was 1.110 chosen for a specific reason (a runtime behavior, a webview or terminal feature, or similar), or was it simply the current release at the time? If it's the latter, could we entertain a PR that lowers the minimum (for example to ^1.75.0 or ^1.100.0)?
I'm happy to test 3.x on 1.103.1 and report back.
Question for you @randy3k:
Throughout the work on 3.0.0, I must confess that I hadn't really noticed that the extension requires VS Code 1.110 or later.
Unfortunately, this is now blocking me at work. We run OpenVSCode Server (not my preferred choice, but a bigger engineering challenge than I'm able to fight rn), and the newest version available to us is 1.103.1. Changing platforms isn't a realistic option in the short term, so I'm stuck on vscode-R 2.8.x :'-(
AFAICT, this requirement came in with the session watcher rewrite in 4e1ca8b (#1684). I couldn't find a stated reason for the bump in the commit, the PR or the changelog. At the same time, I don't think that vscode-R 3.0.0+ actually uses any API newer than 1.75? I asked Claude to investigate and it agreed, pointing out that
@types/vscodeis still pinned at^1.75.0, so any newer API would fail to type-check.Was 1.110 chosen for a specific reason (a runtime behavior, a webview or terminal feature, or similar), or was it simply the current release at the time? If it's the latter, could we entertain a PR that lowers the minimum (for example to
^1.75.0or^1.100.0)?I'm happy to test 3.x on 1.103.1 and report back.