From 458c124b634410575dcb78d0ff99aa5832b6568e Mon Sep 17 00:00:00 2001 From: Andre Weinand Date: Wed, 9 Feb 2022 17:40:55 +0100 Subject: [PATCH] mention Mock Debug for verifying the npm modules --- contributing.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/contributing.md b/contributing.md index e0faefd..3b5db3f 100644 --- a/contributing.md +++ b/contributing.md @@ -21,8 +21,8 @@ Detailled steps: 1. Enter the `protocol` directory, update the `version` in the package.json to a pre-release version like `1.53.0-pre.1`, and `npm publish --tag next`. Wait a bit for npm to propagate these changes. 1. Enter the `adapter` directory, update the `version` in the package.json to a pre-release version _and_ the pre-release version of `@vscode/debugprotocol`, `npm install`, and `npm publish --tag next`. 1. Enter the `testsupport` directory, update the `version` in the package.json to a pre-release version _and_ the pre-release version of `@vscode/debugprotocol`, `npm install`, and `npm publish --tag next`. - - 3. Commit and push the version changes. - 4. At the end of each VS Code iteration (typically Wednesday of endgame week), publish the final version of the three npm packages by removing the pre-release part of the version numbers in the three package.json files and publish them with `npm publish`. - 5. Commit and push the version changes. + 1. Adopt the three new npm modules in [Mock Debug](https://github.com/microsoft/vscode-mock-debug) to verify that they still work. + 1. Commit and push the version changes. + 1. At the end of each VS Code iteration (typically Wednesday of endgame week), publish the final version of the three npm packages by removing the pre-release part of the version numbers in the three package.json files and publish them with `npm publish`. + 1. Commit and push the version changes.