Skip to content

Commit b0029bf

Browse files
committed
Fix markdown that was treated as HTML
1 parent 9855bef commit b0029bf

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/releasing.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,8 @@
1212
* 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.
1313
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:
1414
* `.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
1717
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.
1818
1. Create a PR for this release:
1919
* 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

Comments
 (0)