Skip to content

[Chore]: update vscode to 1.64 #4822

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.

Sign up for GitHub

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

Jump to bottom
Closed
jsjoeio opened this issue Feb 3, 2022 · 4 comments · Fixed by coder/vscode#45 or #4902
Closed

[Chore]: update vscode to 1.64 #4822

jsjoeio opened this issue Feb 3, 2022 · 4 comments · Fixed by coder/vscode#45 or #4902
Assignees
@jsjoeio
Labels
enhancement Some improvement that isn't a feature
Milestone
4.2.0

Comments

@jsjoeio
Copy link
Contributor

jsjoeio commented Feb 3, 2022

https://code.visualstudio.com/updates/v1_64
@jsjoeio jsjoeio added the enhancement Some improvement that isn't a feature label Feb 3, 2022
@jsjoeio jsjoeio added this to the 4.0.3 milestone Feb 3, 2022
@jsjoeio jsjoeio self-assigned this Feb 3, 2022
This was referenced Feb 17, 2022
Closed
Merged
Merged
@jsjoeio jsjoeio mentioned this issue Feb 25, 2022
Closed
3 tasks
@jsjoeio jsjoeio modified the milestones: 4.0.3, March 2022 Mar 2, 2022
@benz0li
Copy link
Contributor

benz0li commented Mar 4, 2022

https://code.visualstudio.com/updates/v1_65 is out.

@jsjoeio
Copy link
Contributor Author

jsjoeio commented Mar 4, 2022

Yes! We saw that. We couldn't finish the 1.64 upgrade in time with the last release (though we could cut another release mid-March if folks wanted). We're in the process of changing the architecture to a patch which will allow us to stay up to date with VS Code much faster.

@jsjoeio jsjoeio mentioned this issue Mar 4, 2022
Closed
@benz0li
Copy link
Contributor

benz0li commented Mar 5, 2022

[...] (though we could cut another release mid-March if folks wanted). [...]

I don't mind if you skip v1.64 and go straight to v1.65 as the base for the next release. I'd suggest you use v1.64 for extended testing of your patch system, then.

@jsjoeio
Copy link
Contributor Author

jsjoeio commented Mar 7, 2022

I don't mind if you skip v1.64 and go straight to v1.65

Since we're almost done we'll upgrade to 1.64 regardless. But ideally we have the patch work done and then can upgrade v1.65.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jsjoeio jsjoeio

Labels
enhancement Some improvement that isn't a feature
Projects
None yet
Milestone
4.2.0
Development

Successfully merging a pull request may close this issue.

feat: upgrade to 1.64 coder/vscode
chore: update vscode to 1.64 coder/code-server
2 participants
@jsjoeio @benz0li