prepare v4 release (#692)

CHANGELOG.md

@@ -8,7 +8,11 @@ Bug-fixes within the same version aren't needed
 * 
 -->
 
-### 4.0.0-alpha.5
+### 4.0.0
+
+* fix internal debug issue with webpack 5.x - @connectdotz (#690)
+* roll up the previous alpha releases...
+#### 4.0.0-alpha.5
 * added setup extension wizard - @connectdotz (#655)
 * update doc to give warning on potential incorrect coverage in watch mode - @connectdotz(#655)
 * Introducing a new interactive mode, in addition to the current "watch" mode, to run jest tests. Use the new `jest.autoRun` settings to control when and what tests should be run automatically, or not. - @connectdotz (#674) 
@@ -19,24 +23,24 @@ Bug-fixes within the same version aren't needed
 * added ability to get jest metadata such as all test files.  - @connectdotz (#674)
 * change editor decorators to reflect when tests are changed but tests have not been run (which might be common in the new interactive mode)  - @connectdotz (#674)
 * addressed a few dependency security vulnerability.
-### 4.0.0-alpha.4
+#### 4.0.0-alpha.4
 * update doc to give warning on potential incorrect coverage in watch mode - @connectdotz
 * fix unknown location bug such as for jest.todo tests (#657) - @connectdotz
 * fix no debug codeLens if autoEnable is false (#658) - @connectdotz
 * turn typescript strict mode on, upgrade tooling and clean up the conflict - @connectdotz
-### 4.0.0-alpha.3
+#### 4.0.0-alpha.3
 * fully support parameterized tests in matching, diagnosis and debugging - @connectdotz
 * optimization: remove stop/start the internal jest tests process during debug - @connectdotz
 * add a new setting for "jest.jestCommandLine" that supersede "jest.pathToJest" and "jest.pathToConfig" - @connectdotz
-### 4.0.0-alpha.2
+#### 4.0.0-alpha.2
 * use assertion's fullName in TestResult instead of the source test name - @connectdotz
 * consolidated and simplified coverage formatter parsing logic; added overlay color customization; change coverage formatter/colors will take effect without restarting vscode; updated coverage help in README. - @connectdotz
-### 4.0.0-alpha.1
+#### 4.0.0-alpha.1
 * change path of jest executable in order to support running jest in yarn workspaces - @glentakahashi
 * refactor editor decorations and load icons from `vscode-codicons` [@Tymek](https://github.com/Tymek)
 * move test status indicator from editor text to gutter [@Tymek](https://github.com/Tymek)
 
-### 4.0.0-alpha.0
+#### 4.0.0-alpha.0
 * improve create-react-app detection logic - stephtr
 * improve the detection of cases in which Jest needs to be restarted with `--watchAll` - [@lordofthelake](https://github.com/lordofthelake)  
 * upgrade all dependencies to the latest, except istanbul-lib-xxx, which requires more code change and will be handled in a separate coverage PR. - @connectdotz

README.md

@@ -3,13 +3,17 @@
 [![Build Status](https://travis-ci.org/jest-community/vscode-jest.svg?branch=master)](https://travis-ci.org/jest-community/vscode-jest) [![Coverage Status](https://coveralls.io/repos/github/jest-community/vscode-jest/badge.svg?branch=master)](https://coveralls.io/github/jest-community/vscode-jest?branch=master) [![Visual Studio Marketplace](https://img.shields.io/visual-studio-marketplace/v/Orta.vscode-jest?color=success&label=Visual%20Studio%20Marketplace)](https://marketplace.visualstudio.com/items?itemName=Orta.vscode-jest) 
 
 ---
-## v4 Pre-Release <!-- omit in toc -->
+## v4 Release <!-- omit in toc -->
 
-We are actively working on our next major release [v4](https://github.com/jest-community/vscode-jest/issues/576) that addresses many nagging issues you have been asking for, such as inconsistent test status indicator, high CPU usage, more granular control of the test runner, missing coverage, supporting parameterized tests, mysterious start up failure etc. 
+After longer than expected development, [v4](https://github.com/jest-community/vscode-jest/releases/tag/v4.0.0) is finally released! 😄
 
-We are now (finally) feature complete with the latest release [v4.0.0-alpha.5](https://github.com/jest-community/vscode-jest/releases/tag/v4.0.0-alpha.5), please feel free to check it out and let us know how it works for you. 
+This is a big release packed with changes to address many nagging issues you have been asking for, such as inconsistent test status indicators, high CPU usage, more granular control of the test runner, missing coverage, supporting parameterized tests, mysterious start up failure etc. 
 
-The current production release (3.2.0) is in code freeze. Please try alpha release if you experienced any issue with the production version. We can most likely fast track your issue right now before the final release.
+Knowing the scope of the changes is significant, while we tried to test it as much as we can, there are probably still some rough edges we have not discovered. If it interrupted your work, our apology! You can either look up on the document below to see if you can find a workaround; or [revert](https://code.visualstudio.com/updates/v1_30#_install-previous-versions) to the earlier version. Please do not hesitate to file [issues](https://github.com/jest-community/vscode-jest/issues) or ask questions in [discussions](https://github.com/jest-community/vscode-jest/discussions), we will be monitoring them closely and address issues as best we can. 
+
+Feel free to read more about the [features and migration](https://github.com/jest-community/vscode-jest/releases/tag/v4.0.0) or come chat with us in the [release discussion](https://github.com/jest-community/vscode-jest/discussions/categories/general) for general comments or questions about this release.
+
+P.S. We find the new version did made the development of this extension a bit easier (yes, we do eat our own dog food :dog:), hopefully, it will do the same for your project. Happy coding!
 
 ---
 
@@ -405,11 +409,21 @@ Sorry you are having trouble with the extension. If your issue did not get resol
 </details>
 
 <details>
-<summary><a id='self-diagnosis'></a>The extension is not behaving as expected, what is going on?</summary> 
+<summary>The tests and status do not match or some tests showing question marks unexpectedly</summary>
+
+If your test file happen to have parameterized tests, i.e. `test.each` variations, please make sure you have jest version >= 26.5. 
+
+If the above did not resolve your issue, please see the [self-diagnosis](#self-diagnosis) below that could show more insight of why the test and result could not be matched.
+
+</details>
+
+<details>
+<summary><a id='self-diagnosis'></a>The extension is not behaving as expected, what is going on? (try self diagnosis)</summary> 
 
 If your can execute jest tests on command line but vscode-jest was not running as expected, here is what you can do to find out more information:
   - See jest process output in the "OUTPUT" channel, which is usually named after the workspace folder, such as `Jest (your-workspace-name)`. Or you can click on `Jest` label on status bar to show Jest Output window. This will show you the jest run output and the errors.
    <img src="https://github.com/jest-community/vscode-jest/raw/master/images/output-channel.png" alt="Screenshot of the tool" width="100%">
+
   - Turn on the debug mode to see more internal debugging message: 
     - set `"jest.debugMode": true` in `.vscode/settings.json` 
     - restart vscode-jest or reload the window (via `Reload Window` command)

package.json

@@ -2,7 +2,7 @@
   "name": "vscode-jest",
   "displayName": "Jest",
   "description": "Use Facebook's Jest With Pleasure.",
-  "version": "4.0.0-alpha.5",
+  "version": "4.0.0",
   "publisher": "Orta",
   "engines": {
     "vscode": "^1.45.0"