Open the VS Code extension test script in VS Code - Insiders
vscode-insiders://ms-dotnettools.dotnet-interactive-vscode/openNotebook?url=https%3A%2F%2Fraw.githubusercontent.com%2Fdotnet%2Finteractive%2Fmain%2FNotebookTestScript.dib
The PR build definition can be found here or by nagivating through an existing PR.
NuGet packages produced from every build of main are auto-published to the NuGet feed https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json
The signed build produces three versions of the VS Code extension, 2 against Stable VS Code and 1 against Insiders. Both versions against Stable append a "0" character to the extension version number and Insiders appends a "1" character.
The Stable extension with the locked tool version can be published via this release definition. This will also immediately publish the corresponding Insiders version of the extension.
The Stable extension with the latest tool can be published via this release definition. This will also immediately publish the corresponding Insiders version of the extension.
The Insiders extension with the latest tool can be published via this release definition.
Once any of those release definitions are invoked, the new extension will appear in the VS Code marketplace approximately 10 minutes later, after the marketplace has run their own internal validation.
The publish/verification script is located in this repo at eng/publish/PublishVSCodeExtension.ps1.
To roll back to a previous build, you'll need to:
- Find the build you'd like to roll back to.
- Copy the commit's SHA.
- Start a new signed build with that SHA.
- Use that build to publish like normal.
This ensures that the version number of the extension is always increasing to pass the VS Code Marketplace verification.
The public GitHub code is internally mirrored here to enable signed builds. You'll likely never need to do anything with this.