prepare alpha-5 (#680)

CHANGELOG.md

@@ -4,6 +4,10 @@ Please add your own contribution below inside the Master section
 Bug-fixes within the same version aren't needed
 
 ## Master
+
+-->
+
+### 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) 
@@ -13,8 +17,7 @@ Bug-fixes within the same version aren't needed
 * added ability to update snapshot without restarting jest.  - @connectdotz (#674)
 * 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
 * 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

README.md

@@ -5,11 +5,11 @@
 ---
 ## v4 Pre-Release <!-- omit in toc -->
 
-We are actively working on our next major release [v4](#576) that fixes many of the nagging issues many of you have asked, such as inconsistent test status indicator, high CPU usage, more granular control of when to run which tests, missing coverage, not recognize parameterized tests, frustrating start up failure etc. 
+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. 
 
-The latest release is [v4.0.0-alpha.4](https://github.com/jest-community/vscode-jest/releases/tag/v4.0.0-alpha.4). 
+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. 
 
-We would love to have as many people try it as possible so we can shake out the bugs and get to the final release sooner. If you experience any issue with the production version, please try the alpha and let us know if it did not fix your issue so we can fast track your issue...
+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.
 
 ---
 

package.json

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

src/TestResults/match-by-context.ts

@@ -179,7 +179,6 @@ const ContextMatch = (messaging: Messaging): ContextMatchAlgorithm => {
       // if we can't find corresponding container to match, the whole container will be considered unmatched
       return toUnmatchedResults(t, `can not find matching assertion for block ${t.name}`, reason);
     }
-    // eslint-disable-next-line @typescript-eslint/no-use-before-define
     return matchContainers(t, matched[0]);
   };