Skip to content
This repository has been archived by the owner on Aug 29, 2021. It is now read-only.

Update all (major) #136

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update all (major) #136

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 29, 2019 •
edited

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/mocha 5.2.6 -> 8.2.2 age adoption passing confidence
@types/node 10.12.27 -> 14.17.3 age adoption passing confidence
@types/rimraf 2.0.2 -> 3.0.0 age adoption passing confidence
husky (source) 1.3.1 -> 6.0.0 age adoption passing confidence
js-combinatorics ^0.5.4 -> ^1.0.0 age adoption passing confidence
mocha (source) 6.0.2 -> 9.0.0 age adoption passing confidence
prettier (source) 1.16.4 -> 2.3.1 age adoption passing confidence
pretty-quick 1.10.0 -> 3.1.0 age adoption passing confidence
rimraf 2.6.3 -> 3.0.2 age adoption passing confidence
ts-mocha 6.0.0 -> 8.0.0 age adoption passing confidence
tslib (source) ^1.9.3 -> ^2.0.0 age adoption passing confidence
typescript (source) 3.3.3333 -> 4.3.2 age adoption passing confidence
vscode-json-languageservice ^3.2.0 -> ^4.0.0 age adoption passing confidence
vscode-languageserver ^5.2.1 -> ^7.0.0 age adoption passing confidence
vscode-uri ^1.0.6 -> ^3.0.0 age adoption passing confidence

Release Notes

typicode/husky

v6.0.0

Compare Source

After being in early access for Open Source projects and Sponsors for a limited time, I'm happy to announce that husky 6 is MIT again and can be freely used in commercial projects! 🎉

Many thanks to the Open Source projects and Companies which have switched to/sponsored the new husky during this period!

OSS is my full-time job, please consider sponsoring the development of husky on GitHub sponsors or Open Collective. Thank you!

Breaking change

  • husky init has been moved to its own package (npx husky-init)

Added

  • Programmatically use husky: require('husky')
  • TypeScript definitions

Migrating from husky 4

Husky 6 contains breaking changes. If you're coming from v4, npm install husky@6 won't be enough.

Recommended: see husky-4-to-6 CLI to automatically migrate your config. There's also a dedicated section in the docs.

If you're curious why config has changed, you may be interested in reading:
https://blog.typicode.com/husky-git-hooks-javascript-config/

Also Husky 6 follows official npm and Yarn best practices regarding autoinstall. It's recommended to use prepare script instead (see usage in docs).

v5.2.0

Compare Source

  • Add set command to replace hooks (husky set .husky/pre-commit cmd)
  • Update add command to append command (husky add .husky/pre-commit cmd)
  • Improve error messages

v5.1.3

Compare Source

  • docs: add specific Yarn v2 install/uninstall instructions
  • cli: husky init will detect Yarn v2 and initialize accordingly

v5.1.2

Compare Source

  • docs: recommend prepare script instead of postinstall (#​890)
  • cli: husky init use prepare script (#​890)

v5.1.1

Compare Source

  • style(shell): add trailing newlines (#​870)
  • fix(init): update package.json postinstall

v5.1.0

Compare Source

  • Add husky init

v5.0.9

Compare Source

  • fix(install): do not fail if not inside a Git directory (closes #​851)

See https://github.com/typicode/husky/releases/tag/v5.0.0 for v5 release notes

v5.0.8

Compare Source

v5.0.7

Compare Source

  • fix(shell): double quote params (#​824)

v5.0.6

Compare Source

  • Remove unused files

v5.0.5

Compare Source

  • Fix custom directory support #​827

v5.0.4

Compare Source

v5.0.3

Compare Source

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

👉 See https://typicode.github.io/husky for breaking changes and new installation instructions.

Note about the license

Husky 5 is released under The Parity Public License.

It doesn't affect you if you're using husky in an Open Source project or if you're a sponsor. You're free to use it as usual and I hope you'll enjoy this new release ❤️

If you're using husky in a commercial project, you may want to consider becoming a sponsor to support the project. You can also try it for 30 days.

This is only for a limited time, husky will be MIT again later.

Migrating

Important Husky v5 brings a lot of improvements but is also very different from v4. Git hooks won't work if you only upgrade husky dependency, existing config needs to be migrated too.

The best way to switch to v5 is to follow the new installation instructions and migrate existing hooks command using husky add.

v4.3.8

Compare Source

  • Fix Cannot read property 'toString' of null
  • Improve error messages

v4.3.7

Compare Source

v4.3.6

Compare Source

  • Fix prepare-commit-msg on windows #​737

v4.3.5

Compare Source

  • Rollback and do not throw error if husky install fails

v4.3.4

Compare Source

  • Throw error if husky install fails
  • Add workaround for npm 7 currently missing INIT_CWD environment variable

v4.3.3

Compare Source

v4.3.2

Compare Source

v4.3.1

Compare Source

v4.3.0

Compare Source

  • Add .cjs config file support #​754

v4.2.5

Compare Source

v4.2.4

Compare Source

  • When Node version is unsupported, log actual version in addition to the error message #​701
  • Fix: support cnpm package manager #​687
  • Fix: always use sh to run scripts and avoid inconsistencies #​707
  • Fix: don't throw error if files are already removed during uninstall #​708

v4.2.3

Compare Source

  • Fix: check for husky.config.js not .huskyrc.config.js #​669

v4.2.2

Compare Source

  • Fix #​662 disable fast-skip heuristic for .husky.js and .husky.config.js
  • Fix do not install update, pre/post-receive hooks

v4.2.1

Compare Source

  • Fix: support spaces in path to husky.local.sh #​658

v4.2.0

Compare Source

  • Check Git version during install and log an error if it's <2.13.0

v4.1.0

Compare Source

  • Improve speed and refactor hooks

v4.0.10

Compare Source

v4.0.9

Compare Source

  • Fix: read stdin from hook script (#​645)

v4.0.8

Compare Source

v4.0.7

Compare Source

  • Fix: Yarn when running inside winpty (#​634)

v4.0.6

Compare Source

  • Revert change in v4.0.5

v4.0.5

Compare Source

  • Fix: use process.exit if install fails #​633

v4.0.4

Compare Source

  • Fix: npm ignore .eslintrc.js (#​627)

v4.0.3

Compare Source

  • Fix: error message if trying to install in a non-git repo (#​627)

v4.0.2

Compare Source

  • Fix: show error message when hook fails

v4.0.1

Compare Source

  • Fix: make Yarn silent. When Husky was installed with Yarn 1.21.1, hooks output was too verbose (#​626).

v4.0.0

Compare Source

  • Support Yarn v2 new Plug'n'Play feature (thanks to @​arcanis)
  • Improve path handling on Windows (in particular with Cygwin and Cmdr)
  • Remove dependencies and simplify code
  • Breaking requires Node 10+

Thanks to all contributors and everyone who is supporting Husky on Open Collective, GitHub sponsors and Patreon!

v3.1.0

Compare Source

  • Add pre-merge-commit hook (#​605)

v3.0.9

Compare Source

  • Reduce dependencies: replace is-ci with ci-info #​579

v3.0.8

Compare Source

  • Fix: git worktree support #​580
  • Debug: check GIT_DIR environment variable when hooks are run

v3.0.7

Compare Source

Debug: display husky version and created at

v3.0.6

Compare Source

Debug: improve messages

v3.0.5

Compare Source

Fix: prevent postinstall from failing on windows typicode/husky#573

v3.0.4

Compare Source

Fix: skip install earlier when HUSKY_SKIP_INSTALL=1 (typicode/husky#563)

v3.0.3

Compare Source

Fix: prevent old hooks (husky < 1.0) to be run if new ones are defined (husky >= 1.0 ) typicode/husky#556

v3.0.2

Compare Source

  • Fix: add shebang to run.js (#​528)

v3.0.1

Compare Source

  • Improve error message if git command fails

v3.0.0

Compare Source

  • Fix HUSKY_SKIP_INSTALL=1 not skipping install
  • Breaking change husky requires now Git >= 2.13.2. If you're already using husky v2 and don't use an old version of Git, you can safely upgrade.

v2.7.0

Compare Source

v2.6.0

Compare Source

v2.5.0

Compare Source

v2.4.1

Compare Source

v2.4.0

Compare Source

v2.3.0

Compare Source

v2.2.0

Compare Source

v2.1.0

Compare Source

v2.0.0

Compare Source

dankogai/js-combinatorics

v1.4.5

Compare Source

v1.4.4

Compare Source

v1.4.3

Compare Source

v1.4.2

Compare Source

v1.4.1

Compare Source

v1.4.0

Compare Source

v1.3.0

Compare Source

v1.2.3

Compare Source

v1.2.2

Compare Source

v1.2.1

Compare Source

v1.2.0

Compare Source

v1.1.1

Compare Source

v1.1.0

Compare Source

v1.0.0

Compare Source

v0.6.1

Compare Source

v0.6.0

Compare Source

mochajs/mocha

v9.0.0

Compare Source

💥 Breaking Changes

Mocha is going ESM-first! This means that it will now use ESM import(test_file) to load the test files, instead of the CommonJS require(test_file). This is not a problem, as import can also load most files that require does. In the rare cases where this fails, it will fallback to require(...). This ESM-first approach is the next step in Mocha's ESM migration, and allows ESM loaders to load and transform the test file.

🎉 Enhancements

🐛 Fixes

🔩 Other

v8.4.0

Compare Source

🎉 Enhancements

🐛 Fixes

📖 Documentation

Also thanks to @​outsideris for various improvements on our GH actions workflows.

v8.3.2

Compare Source

🐛 Fixes

📖 Documentation

v8.3.1

Compare Source

🐛 Fixes

v8.3.0

Compare Source

🎉 Enhancements

🐛 Fixes

📖 Documentation

🔩 Other

Also thanks to @​outsideris and @​HyunSangHan for various fixes to our website and documentation.

v8.2.1

Compare Source

Fixed stuff.

🐛 Fixes

  • #​4489: Fix problematic handling of otherwise-unhandled Promise rejections and erroneous "done() called twice" errors (@​boneskull)
  • #​4496: Avoid MaxListenersExceededWarning in watch mode (@​boneskull)

Also thanks to @​akeating for a documentation fix!

v8.2.0

Compare Source

The major feature added in v8.2.0 is addition of support for 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, 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:

// 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 and this handy-dandy flowchart to help understand the differences between hooks, root hook plugins, and global fixtures (and when you should use each).

🎉 Enhancements

For implementors of custom reporters:

  • #​4409: Parallel mode and custom reporter improvements (@​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())

🐛 Fixes

  • #​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)
  • #​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)
  • #​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)

Thanks to @​AviVahl, @​donghoon-song, @​ValeriaVG, @​znarf, @​sujin-park, and @​majecty for other helpful contributions!

v8.1.3

Compare Source

🐛 Fixes

  • #​4425: Restore Mocha.utils.lookupFiles() and Webpack compatibility (both broken since v8.1.0); Mocha.utils.lookupFiles() is now deprecated and will be removed in the next major revision of Mocha; use require('mocha/lib/cli').lookupFiles instead (@​boneskull)

v8.1.2

Compare Source

🐛 Fixes

🔒 Security Fixes

📖 Documentation

v8.1.1

Compare Source

🐛 Fixes

  • #​4394: Fix regression wherein certain reporters did not correctly detect terminal width (@​boneskull)

v8.1.0

Compare Source

In this release, Mocha now builds its browser bundle with Rollup and Babel, which will provide the project's codebase more flexibility and consistency.

While we've been diligent about backwards compatibility, it's possible consumers of the browser bundle will encounter differences (other than an increase in the bundle size). If you do encounter an issue with the build, please report it here.

This release does not drop support for IE11.

Other community contributions came from @​Devjeel, @​Harsha509 and @​sharath2106. Thank you to everyone who contributed to this release!

Do you read Korean? See this guide to running parallel tests in Mocha, translated by our maintainer, @​outsideris.

🎉 Enhancements

🐛 Fixes

🔒 Security Fixes

📖 Documentation & Website

🔩 Other

  • #​4293: Use Rollup and Babel in build pipeline; add source map to published files (@​Munter)

v8.0.1

Compare Source

The obligatory patch after a major.

🐛 Fixes

v8.0.0

Compare Source

In this major release, Mocha adds the ability to run tests in parallel. Better late than never! Please note the breaking changes detailed below.

Let's welcome @​giltayar and @​nicojs to the maintenance team!

💥 Breaking Changes

  • #​4164: Mocha v8.0.0 now requires Node.js v10.12.0 or newer. Mocha no longer supports the Node.js v8.x line ("Carbon"), which entered End-of-Life at the end of 2019 (@​UlisesGascon)

  • #​4175: Having been deprecated with a warning since v7.0.0, mocha.opts is no longer supported (@​juergba)

    ✨ WORKAROUND: Replace mocha.opts with a configuration file.

  • #​4260: Remove enableTimeout() (this.enableTimeout()) from the context object (@​craigtaub)

    ✨ WORKAROUND: Replace usage of this.enableTimeout(false) in your tests with this.timeout(0).

  • #​4315: The spec option no longer supports a comma-delimited list of files (@​juergba)

    ✨ WORKAROUND: Use an array instead (e.g., "spec": "foo.js,bar.js" becomes "spec": ["foo.js", "bar.js"]).

  • #​4309: Drop support for Node.js v13.x line, which is now End-of-Life (@​juergba)

  • #​4282: --forbid-only will throw an error even if exclusive tests are avoided via --grep or other means (@​arvidOtt)

  • #​4223: The context object's skip() (this.skip()) in a "before all" (before()) hook will no longer execute subsequent sibling hooks, in addition to hooks in child suites (@​juergba)

  • #​4178: Remove previously soft-deprecated APIs (@​wnghdcjfe):

    • Mocha.prototype.ignoreLeaks()
    • Mocha.prototype.useColors()
    • Mocha.prototype.useInlineDiffs()
    • Mocha.prototype.hideDiff()

🎉 Enhancements

📖 Documentation

🔩 Other

🐛 Fixes

(All bug fixes in Mocha v8.0.0 are also breaking changes, and are listed above)

v7.2.0

Compare Source

🎉 Enhancements

🐛 Fixes

📖 Documentation

🔩 Other

v7.1.2

Compare Source

🔩 Other

📖 Documentation

v7.1.1

Compare Source

🔒 Security Fixes

🐛 Fixes

  • #​3660: Fix runner listening to start a

Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot requested a review from Levertion as a code owner April 29, 2019 00:58
@renovate renovate bot changed the title Update dependency husky to v2 Update all (major) May 29, 2019
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 0b463d3 to fd54bbf Compare June 11, 2019 22:30
@renovate renovate bot force-pushed the renovate/major-all branch 4 times, most recently from 351e418 to e3becec Compare June 27, 2019 15:42
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 1417693 to a78c284 Compare January 9, 2021 21:59
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 60eee41 to 7e4b0e0 Compare February 10, 2021 23:52
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 875f5c2 to a5d75f2 Compare May 15, 2021 21:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@Levertion Levertion Awaiting requested review from Levertion Levertion is a code owner

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@renovate-bot