You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
[...] (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.
Activity
benz0li commentedon Mar 4, 2022
https://code.visualstudio.com/updates/v1_65 is out.
jsjoeio commentedon 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.
benz0li commentedon Mar 5, 2022
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 commentedon Mar 7, 2022
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.