This repository has been archived by the owner on Aug 29, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Update all (major) #136
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-all
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update all (major) #136
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/major-all
branch
from
May 2, 2019 03:40
a96031b
to
4be99ee
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
May 14, 2019 17:03
4be99ee
to
4086a81
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
May 29, 2019 11:05
4086a81
to
d113219
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
June 11, 2019 22:30
0b463d3
to
fd54bbf
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
4 times, most recently
from
June 27, 2019 15:42
351e418
to
e3becec
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
July 13, 2019 15:57
e3becec
to
ac6c696
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
August 10, 2019 08:52
ac6c696
to
94f2bfb
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
August 20, 2019 15:59
94f2bfb
to
2464ac6
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
September 5, 2019 01:58
2464ac6
to
f6bbd44
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
October 4, 2019 13:59
f6bbd44
to
0577f06
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
November 11, 2019 12:58
0577f06
to
1f0bac1
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
November 21, 2019 10:43
1f0bac1
to
9e1b34f
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
January 18, 2020 19:41
9e1b34f
to
b71a496
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
February 8, 2020 20:57
b71a496
to
3e2132e
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
February 21, 2020 06:56
3e2132e
to
0a2c2c9
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
March 15, 2020 06:59
0a2c2c9
to
5e45416
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
May 3, 2020 10:57
5e45416
to
e59bfeb
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
July 1, 2020 16:52
e59bfeb
to
cb3e87a
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
August 27, 2020 06:58
cb3e87a
to
24eabbf
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
October 27, 2020 06:57
24eabbf
to
995f9ea
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
November 26, 2020 19:49
995f9ea
to
25314b0
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
December 9, 2020 15:58
25314b0
to
36bf184
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
January 9, 2021 21:59
1417693
to
a78c284
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
January 24, 2021 15:50
a78c284
to
048f3e1
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
February 10, 2021 23:52
60eee41
to
7e4b0e0
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
April 26, 2021 15:49
7e4b0e0
to
9604707
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
May 15, 2021 21:11
875f5c2
to
a5d75f2
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
June 6, 2021 22:04
a5d75f2
to
c4aa698
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
June 12, 2021 20:10
c4aa698
to
8892dc7
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.2.6
->8.2.2
10.12.27
->14.17.3
2.0.2
->3.0.0
1.3.1
->6.0.0
^0.5.4
->^1.0.0
6.0.2
->9.0.0
1.16.4
->2.3.1
1.10.0
->3.1.0
2.6.3
->3.0.2
6.0.0
->8.0.0
^1.9.3
->^2.0.0
3.3.3333
->4.3.2
^3.2.0
->^4.0.0
^5.2.1
->^7.0.0
^1.0.6
->^3.0.0
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
require('husky')
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
set
command to replace hooks (husky set .husky/pre-commit cmd
)add
command to append command (husky add .husky/pre-commit cmd
)v5.1.3
Compare Source
husky init
will detect Yarn v2 and initialize accordinglyv5.1.2
Compare Source
prepare
script instead ofpostinstall
(#890)husky init
useprepare
script (#890)v5.1.1
Compare Source
v5.1.0
Compare Source
husky init
v5.0.9
Compare Source
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
v5.0.6
Compare Source
v5.0.5
Compare Source
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
Cannot read property 'toString' of null
v4.3.7
Compare Source
v4.3.6
Compare Source
prepare-commit-msg
on windows #737v4.3.5
Compare Source
v4.3.4
Compare Source
INIT_CWD
environment variablev4.3.3
Compare Source
v4.3.2
Compare Source
v4.3.1
Compare Source
v4.3.0
Compare Source
.cjs
config file support #754v4.2.5
Compare Source
v4.2.4
Compare Source
cnpm
package manager #687sh
to run scripts and avoid inconsistencies #707v4.2.3
Compare Source
husky.config.js
not.huskyrc.config.js
#669v4.2.2
Compare Source
.husky.js
and.husky.config.js
update
,pre/post-receive
hooksv4.2.1
Compare Source
v4.2.0
Compare Source
<2.13.0
v4.1.0
Compare Source
v4.0.10
Compare Source
v4.0.9
Compare Source
v4.0.8
Compare Source
v4.0.7
Compare Source
winpty
(#634)v4.0.6
Compare Source
v4.0.5
Compare Source
v4.0.4
Compare Source
.eslintrc.js
(#627)v4.0.3
Compare Source
v4.0.2
Compare Source
v4.0.1
Compare Source
v4.0.0
Compare Source
Yarn v2
new Plug'n'Play feature (thanks to @arcanis)Cygwin
andCmdr
)dependencies
and simplify codeNode 10+
Thanks to all contributors and everyone who is supporting Husky on Open Collective, GitHub sponsors and Patreon!
v3.1.0
Compare Source
pre-merge-commit
hook (#605)v3.0.9
Compare Source
is-ci
withci-info
#579v3.0.8
Compare Source
GIT_DIR
environment variable when hooks are runv3.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#573v3.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#556v3.0.2
Compare Source
v3.0.1
Compare Source
v3.0.0
Compare Source
>= 2.13.2
. If you're already using huskyv2
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
#4633: Drop Node.js v10.x support (@juergba)
#4635:
import
-first loading of test files (@giltayar)Mocha is going ESM-first! This means that it will now use ESM
import(test_file)
to load the test files, instead of the CommonJSrequire(test_file)
. This is not a problem, asimport
can also load most files thatrequire
does. In the rare cases where this fails, it will fallback torequire(...)
. This ESM-first approach is the next step in Mocha's ESM migration, and allows ESM loaders to load and transform the test file.#4636: Remove deprecated
utils.lookupFiles()
(@juergba)#4638: Limit the size of
actual
/expected
fordiff
generation (@juergba)#4389: Refactoring: Consuming log-symbols alternate to code for win32 in reporters/base (@MoonSupport)
🎉 Enhancements
--dry-run
(@juergba)🐛 Fixes
🔩 Other
Runner(suite: Suite, delay: boolean)
signature (@juergba)v8.4.0
Compare Source
🎉 Enhancements
🐛 Fixes
📖 Documentation
options.require
to Mocha constructor forroot hook
plugins on parallel runs (@juergba)top-level await
and ESM test files (@juergba)Also thanks to @outsideris for various improvements on our GH actions workflows.
v8.3.2
Compare Source
🐛 Fixes
require
interface (@alexander-fenster)📖 Documentation
v8.3.1
Compare Source
🐛 Fixes
EvalError
caused by regenerator-runtime (@snoack)import
from mocha in parallel mode (@nicojs)v8.3.0
Compare Source
🎉 Enhancements
🐛 Fixes
require
error when bundling Mocha with Webpack (@devhazem)📖 Documentation
🔩 Other
Also thanks to @outsideris and @HyunSangHan for various fixes to our website and documentation.
v8.2.1
Compare Source
Fixed stuff.
🐛 Fixes
Promise
rejections and erroneous "done()
called twice" errors (@boneskull)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-levelbefore()
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 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
test.js
) now usable with--extension
option (@jordanstephens).js
,.test.js
) now usable with--extension
option (@boneskull)json
reporter now containsspeed
("fast"/"medium"/"slow") property (@wwhurin)For implementors of custom reporters:
Runner.prototype.workerReporter()
); reporters should subclassParallelBufferedReporter
inmocha/lib/nodejs/reporters/parallel-buffered
Runner.prototype.linkPartialObjects()
); use if strict object equality is needed when consumingRunner
event dataRunner.prototype.isParallelMode()
)🐛 Fixes
npm
v6.x causing some of Mocha's deps to be installed whenmocha
is present in a package'sdevDependencies
andnpm install --production
is run the package's working copy (@boneskull)nyc
with Mocha in parallel mode (@boneskull)lookupFiles()
inmocha/lib/utils
, which was broken/missing in Mocha v8.1.0; it now prints a deprecation warning (useconst {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
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; userequire('mocha/lib/cli').lookupFiles
instead (@boneskull)v8.1.2
Compare Source
🐛 Fixes
🔒 Security Fixes
📖 Documentation
v8.1.1
Compare Source
🐛 Fixes
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!
🎉 Enhancements
🐛 Fixes
mocha init
(@boneskull)delay
option in browser (@craigtaub)🔒 Security Fixes
📖 Documentation & Website
--enable-source-maps
with Mocha (@bcoe)🔩 Other
v8.0.1
Compare Source
The obligatory patch after a major.
🐛 Fixes
--parallel
when combined with--watch
(@boneskull)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 withthis.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
#4245: Add ability to run tests in parallel for Node.js (see docs) (@boneskull)
❗ See also #4244; Root Hook Plugins (docs) -- root hooks must be defined via Root Hook Plugins to work in parallel mode
#4304:
--require
now works with ES modules (@JacobLey)#4299: In some circumstances, Mocha can run ES modules under Node.js v10 -- use at your own risk! (@giltayar)
📖 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
--forbid-only
does not recognizeit.only
whenbefore
crashes (@arvidOtt)📖 Documentation
🔩 Other
v7.1.2
Compare Source
🔩 Other
📖 Documentation
v7.1.1
Compare Source
🔒 Security Fixes
🐛 Fixes
runner
listening tostart
aConfiguration
📅 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.