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
Copy file name to clipboardExpand all lines: docs/releasing.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,8 +12,8 @@
12
12
* Accumulation of many changes, none of which are individually big enough to warrant a minor bump, but which together are. This does not include changes which are purely internal to the extension, such as refactoring, or which are only available behind a feature flag.
13
13
1. Double-check that the node version we're using matches the one used for VS Code. If it doesn't, you will then need to update the node version in the following files:
14
14
*`.nvmrc` - this will enable `nvm` to automatically switch to the correct node version when you're in the project folder
15
-
*`.github/workflows/main.yml` - all the "node-version: <version>" settings
16
-
*`.github/workflows/release.yml` - the "node-version: <version>" setting
15
+
*`.github/workflows/main.yml` - all the "node-version: '[VERSION]'" settings
16
+
*`.github/workflows/release.yml` - the "node-version: '[VERSION]'" setting
17
17
1. Double-check that the extension `package.json` and `package-lock.json` have the version you intend to release. If you are doing a patch release (as opposed to minor or major version) this should already be correct.
18
18
1. Create a PR for this release:
19
19
* This PR will contain any missing bits from steps 1, 2 and 3. Most of the time, this will just be updating `CHANGELOG.md` with today's date.
0 commit comments