Closed renovate[bot] closed 4 years ago
This PR will trigger no release when merged.
Merging #327 into master will increase coverage by
0.06%
. The diff coverage is100.00%
.
@@ Coverage Diff @@
## master #327 +/- ##
==========================================
+ Coverage 98.68% 98.75% +0.06%
==========================================
Files 7 7
Lines 228 240 +12
==========================================
+ Hits 225 237 +12
Misses 3 3
Impacted Files | Coverage Δ | |
---|---|---|
src/embed.js | 96.66% <100.00%> (+0.46%) |
:arrow_up: |
src/index.js | 100.00% <100.00%> (ø) |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update e441a17...c7c62d9. Read the comment docs.
:tada: This PR is included in version 1.9.0 :tada:
The release is available on:
v1.9.0
Your semantic-release bot :package::rocket:
This PR contains the following updates:
8.1.3
->8.2.0
17.1.2
->17.2.1
Release Notes
mochajs/mocha
### [`v8.2.0`](https://togithub.com/mochajs/mocha/blob/master/CHANGELOG.md#820--2020-10-16) [Compare Source](https://togithub.com/mochajs/mocha/compare/v8.1.3...v8.2.0) The major feature added in v8.2.0 is addition of support for [_global fixtures_](https://mochajs.org/#global-fixtures). While Mocha has always had the ability to run setup and teardown via a hook (e.g., a `before()` at the top level of a test file) when running tests in serial, Mocha v8.0.0 added support for parallel runs. Parallel runs are _incompatible_ with this strategy; e.g., a top-level `before()` would only run for the file in which it was defined. With [global fixtures](https://mochajs.org/#global-fixtures), Mocha can now perform user-defined setup and teardown _regardless_ of mode, and these fixtures are guaranteed to run _once and only once_. This holds for parallel mode, serial mode, and even "watch" mode (the teardown will run once you hit Ctrl-C, just before Mocha finally exits). Tasks such as starting and stopping servers are well-suited to global fixtures, but not sharing resources--global fixtures do _not_ share context with your test files (but they do share context with each other). Here's a short example of usage: ```js // fixtures.js // can be async or not exports.mochaGlobalSetup = async function() { this.server = await startSomeServer({port: process.env.TEST_PORT}); console.log(`server running on port ${this.server.port}`); }; exports.mochaGlobalTeardown = async function() { // the context (`this`) is shared, but not with the test files await this.server.stop(); console.log(`server on port ${this.server.port} stopped`); }; // this file can contain root hook plugins as well! // exports.mochaHooks = { ... } ``` Fixtures are loaded with `--require`, e.g., `mocha --require fixtures.js`. For detailed information, please see the [documentation](https://mochajs.org/#global-fixtures) and this handy-dandy [flowchart](https://mochajs.org/#test-fixture-decision-tree-wizard-thing) to help understand the differences between hooks, root hook plugins, and global fixtures (and when you should use each). #### :tada: Enhancements - [#4308](https://togithub.com/mochajs/mocha/issues/4308): Support run-once [global setup & teardown fixtures](https://mochajs.org/#global-fixtures) ([**@boneskull**](https://togithub.com/boneskull)) - [#4442](https://togithub.com/mochajs/mocha/issues/4442): Multi-part extensions (e.g., `test.js`) now usable with `--extension` option ([**@jordanstephens**](https://togithub.com/jordanstephens)) - [#4472](https://togithub.com/mochajs/mocha/issues/4472): Leading dots (e.g., `.js`, `.test.js`) now usable with `--extension` option ([**@boneskull**](https://togithub.com/boneskull)) - [#4434](https://togithub.com/mochajs/mocha/issues/4434): Output of `json` reporter now contains `speed` ("fast"/"medium"/"slow") property ([**@wwhurin**](https://togithub.com/wwhurin)) - [#4464](https://togithub.com/mochajs/mocha/issues/4464): Errors thrown by serializer in parallel mode now have error codes ([**@evaline-ju**](https://togithub.com/evaline-ju)) _For implementors of custom reporters:_ - [#4409](https://togithub.com/mochajs/mocha/issues/4409): Parallel mode and custom reporter improvements ([**@boneskull**](https://togithub.com/boneskull)): - Support custom worker-process-only reporters (`Runner.prototype.workerReporter()`); reporters should subclass `ParallelBufferedReporter` in `mocha/lib/nodejs/reporters/parallel-buffered` - Allow opt-in of object reference matching for "sufficiently advanced" custom reporters (`Runner.prototype.linkPartialObjects()`); use if strict object equality is needed when consuming `Runner` event data - Enable detection of parallel mode (`Runner.prototype.isParallelMode()`) #### :bug: Fixes - [#4476](https://togithub.com/mochajs/mocha/issues/4476): Workaround for profoundly bizarre issue affecting `npm` v6.x causing some of Mocha's deps to be installed when `mocha` is present in a package's `devDependencies` and `npm install --production` is run the package's working copy ([**@boneskull**](https://togithub.com/boneskull)) - [#4465](https://togithub.com/mochajs/mocha/issues/4465): Worker processes guaranteed (as opposed to "very likely") to exit before Mocha does; fixes a problem when using `nyc` with Mocha in parallel mode ([**@boneskull**](https://togithub.com/boneskull)) - [#4419](https://togithub.com/mochajs/mocha/issues/4419): Restore `lookupFiles()` in `mocha/lib/utils`, which was broken/missing in Mocha v8.1.0; it now prints a deprecation warning (use `const {lookupFiles} = require('mocha/lib/cli')` instead) ([**@boneskull**](https://togithub.com/boneskull)) Thanks to [**@AviVahl**](https://togithub.com/AviVahl), [**@donghoon-song**](https://togithub.com/donghoon-song), [**@ValeriaVG**](https://togithub.com/ValeriaVG), [**@znarf**](https://togithub.com/znarf), [**@sujin-park**](https://togithub.com/sujin-park), and [**@majecty**](https://togithub.com/majecty) for other helpful contributions!semantic-release/semantic-release
### [`v17.2.1`](https://togithub.com/semantic-release/semantic-release/releases/v17.2.1) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v17.2.0...v17.2.1) ##### Reverts - Revert "feat: throw an Error if package.json has duplicate "repository" key ([#1656](https://togithub.com/semantic-release/semantic-release/issues/1656))" ([3abcbaf](https://togithub.com/semantic-release/semantic-release/commit/3abcbaf2561a208180a1f8eddc1d8a5c1006fe48)), closes [#1656](https://togithub.com/semantic-release/semantic-release/issues/1656) [#1657](https://togithub.com/semantic-release/semantic-release/issues/1657) ### [`v17.2.0`](https://togithub.com/semantic-release/semantic-release/releases/v17.2.0) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v17.1.2...v17.2.0) ##### Features - throw an Error if package.json has duplicate "repository" key ([#1656](https://togithub.com/semantic-release/semantic-release/issues/1656)) ([b8fb35c](https://togithub.com/semantic-release/semantic-release/commit/b8fb35c7e15d314c15182f779ef30b42b6c4e7ea))Renovate configuration
:date: Schedule: "after 2pm on Saturday" in timezone Europe/Zurich.
:vertical_traffic_light: Automerge: Disabled due to failing status checks.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by WhiteSource Renovate. View repository job log here.