-
Notifications
You must be signed in to change notification settings - Fork 5.9k
[Feat]: Upgrade to vscode 1.69 #5344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think 1.69.2 is out now so I changed title to major.minor to count for both |
@code-asher @jsjoeio we are always 1 minor release behind the vscode. currently, we are in 1.68 while vscode is in 1.69. by the time aug 2022 is released, vscode may move to 1.70. Can we have an intermediate upgrade release closest to vscode release schedule? The vscode upgraded release may help resolve some issues in our existing issues list as well as submit any new bugs. since it is only users option to install upgrade, interested users will install and let us know any new bugs. this will also keep us close to vscode release schedule and help us tryout the same features in vscode desktop. |
@bala yeah, you're right. I mean we're trying as best we can to keep up but it's been very tough lately. We're at a company off-site this week for example. @code-asher and I can discuss this with @misskniss @tjcran to see how we can improve our VS Code upgrade and release cadence to be more in line with upstream. Thanks for the suggestion! |
vscode 1.70 is out: https://github.com/microsoft/vscode/releases/tag/1.70.0 |
#5417 [Feat]: Upgrade vscode to 1.70 is opened separately |
First patches for 1.70 #5422 look good. Jupyter, |
Completed via #5422 |
What is your suggestion?
Upgrade to vscode 1.69.1
The text was updated successfully, but these errors were encountered: