Repository navigation
3.2.0 release #1824
Description
Activity
Agree
Agree
SGTM. #1832 was (is) a necessary condition for me to be able to use vscode-R at work, so I'd be grateful to have that available in the release version ASAP.
P.S. I imagine that this would be taken care of as part of the release, but the
sessversioning seems to be out of whack. It's currently denominated as3.0.9000.9001.P.S. I imagine that this would be taken care of as part of the release, but the
sessversioning seems to be out of whack. It's currently denominated as3.0.9000.9001.As far as I understand, this is not a problem because vscode-R no longer checks for the sess version.
Good to know, but I still think we should fix the versioning (the double
*.9000.9001semantic suffix is strange, right?)#1832 was (is) a necessary condition for me to be able to use vscode-R at work, so I'd be grateful to have that available in the release version ASAP.
Could you try daily pre-release version?
Please check README.
To receive daily development updates, choose Switch to Pre-Release Version on the R extension's page in VS Code. New pre-releases are published to the VS Code Marketplace and Open VSX Registry when main changes and verification passes. Choose Switch to Release Version to return to stable releases. When reporting problems, include the extension version and reproduction steps.
Thanks @eitsupi , confirmed that works locally. But my work situation requires a containerised solution, with pinned versions of our different SW, so I'd prefer to wait for the formal 3.2 release. (Otherwise my SDE team is going to get grumpy.)
As an aside, I think it could be simpler to give the CLI equivalent of the above steps in the README, which is just:
code --install-extension REditorSupport.r --pre-release --force
I've created https://github.com/REditorSupport/vscode-R/milestone/4
Since a lot of changes have been made, I think we could consider releasing version 3.1.0.
@renkun-ken @Fred-Wu
Do you have any thoughts on that?