Preparing the release candidate. #15900
Conversation
| ([#15580](https://github.com/Microsoft/vscode-python/issues/15580)) | ||
| 1. Ensure that jedi language server uses jedi shipped with the extension. | ||
| ([#15586](https://github.com/Microsoft/vscode-python/issues/15586)) | ||
| 1. Updates to Proposed API, and fix the failure in VS Code Insider tests. |
There was a problem hiding this comment.
Is the Python release aligned with VS Code's stable release cycle? This fix that I made here to unblock insiders was only checked into VS Code main 13 days ago, so it's only live on insiders and not on stable yet. I might have to adjust this to handle either the old API or the new API if this goes live before then.
There was a problem hiding this comment.
Our release is not aligned with VS Code's release cycle. So I guess we need this fix before we release.
There was a problem hiding this comment.
@luabud Yeah, sorry about the complication here. Given that we want to keep main running with insiders builds I think that splitting off release is still fine. I'll just have to make a fix directly into the release branch for this.
There was a problem hiding this comment.
@IanMatthewHuff sounds good, thank you!! 😊
6 participants
Looks like i accidentally did not merge the change log back from release. Fixed that here.