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: CONTRIBUTING.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -229,6 +229,13 @@ Pre-recorded scenarios are stored in `./src/mocks/scenarios`. However, it's poss
229
229
1. Double-check the `CHANGELOG.md` contains all desired change comments and has the version to be released with date at the top.
230
230
* Go through all recent PRs and make sure they are properly accounted for.
231
231
* Make sure all changelog entries have links back to their PR(s) if appropriate.
232
+
* For picking the new version number, we default to increasing the patch version number, but make our own judgement about whether a change is big enough to warrant a minor version bump. Common reasons for a minor bump could include:
233
+
* Making substantial new features available to all users. This can include lifting a feature flag.
234
+
* Breakage in compatibility with recent versions of the CLI.
235
+
* Minimum required version of VS Code is increased.
236
+
* New telemetry events are added.
237
+
* Deprecation or removal of commands.
238
+
* 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.
232
239
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:
233
240
*`.nvmrc` - this will enable `nvm` to automatically switch to the correct node version when you're in the project folder
234
241
*`.github/workflows/main.yml` - all the "node-version: <version>" settings
0 commit comments