chore(deps): update all (major) #8
Open
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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/major-all
branch
3 times, most recently
from
c1be7e3
to
5913a36
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
6 times, most recently
from
641558f
to
bede3e2
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
bede3e2
to
6834b09
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
4 times, most recently
from
565687e
to
bdd9f11
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
bdd9f11
to
9536983
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
4 times, most recently
from
eb90118
to
2fafb6a
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
4 times, most recently
from
bd01d23
to
baab0b8
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
6 times, most recently
from
960fb75
to
362a765
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
8418e05
to
a4001c6
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
a4001c6
to
0120f6a
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
3 times, most recently
from
771e61e
to
8c78e16
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
fd1de32
to
c4f69a8
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
d975591
to
a76e2ab
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
a76e2ab
to
0409cca
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
3 times, most recently
from
3f96e57
to
c1240c2
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
0b06868
to
4160fc4
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
323527d
to
0408d1e
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
6 times, most recently
from
3935966
to
4546ab8
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
4 times, most recently
from
be2ee19
to
1ca30a3
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
1ca30a3
to
11ce0cd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
1.12.0->3.0.2v4.0.2+incompatible->v5.0.120.7.20->10.9.12.2.0->3.2.01.1.2->2.2.11.2.0->2.1.31.3.0->2.0.11.21.5->10.4.00.68.2->4.18.02.3.1->4.0.02.8.29->3.17.4Release Notes
kurttheviking/git-rev-sync-js (git-rev-sync)
v3.0.2Compare Source
v3.0.1Compare Source
v3.0.0Compare Source
v2.1.0Compare Source
v2.0.0Compare Source
go-chi/chi (github.com/go-chi/chi)
v5.0.12Compare Source
v5.0.11Compare Source
v5.0.10Compare Source
v5.0.9Compare Source
v5.0.8Compare Source
v5.0.7Compare Source
v5.0.6Compare Source
v5.0.5Compare Source
v5.0.4Compare Source
v5.0.3Compare Source
v5.0.2Compare Source
v5.0.1Compare Source
v5.0.0Compare Source
github.com/go-chi/chi/v5introduces the adoption of Go's SIV to adhere to the current state-of-the-tools in Go.The most responsible thing to do for everyone's benefit is to just release v5 with SIV, so I present to you all,
chi v5 at
github.com/go-chi/chi/v5. I hope someday the developer experience and ergonomics I've been seekingwill still come to fruition in some form, https://github.com/golang/go/issues/445504550
v4.1.3Compare Source
v4.1.2Compare Source
v4.1.2+incompatibleCompare Source
v4.1.1Compare Source
route to the correct handler through a recursive tree search, thanks to @Jahaja for the PR/fix!
v4.1.1+incompatibleCompare Source
v4.1.0Compare Source
and an extra interface type useful for custom logger implementations.
v4.1.0+incompatibleCompare Source
v4.0.4Compare Source
v4.0.4+incompatibleCompare Source
v4.0.3Compare Source
v4.0.3+incompatibleCompare Source
jakejs/jake (jake)
v10.9.1Compare Source
v10.8.7Compare Source
v10.8.6Compare Source
v10.8.5Compare Source
v10.8.2Compare Source
v10.8.1Compare Source
v10.7.1Compare Source
v10.6.1Compare Source
v10.5.2Compare Source
v10.4.7Compare Source
v10.4.6Compare Source
v10.4.5Compare Source
v10.4.4Compare Source
v10.4.3Compare Source
v10.4.2Compare Source
v10.4.1Compare Source
v10.3.2Compare Source
v10.3.1Compare Source
v10.3.0Compare Source
v10.1.11Compare Source
v10.1.10Compare Source
v10.1.9Compare Source
v10.1.7Compare Source
v10.1.6Compare Source
v10.1.5Compare Source
v10.1.4Compare Source
v10.1.3Compare Source
v10.1.2Compare Source
v10.1.1Compare Source
v10.0.6Compare Source
v10.0.3Compare Source
v10.0.2Compare Source
v8.1.1Compare Source
v8.0.19Compare Source
v8.0.18Compare Source
v8.0.16Compare Source
v8.0.15Compare Source
v8.0.14Compare Source
v8.0.12Compare Source
v8.0.11Compare Source
v8.0.10Compare Source
v8.0.9Compare Source
v8.0.8Compare Source
v8.0.6Compare Source
v8.0.5Compare Source
v8.0.4Compare Source
v8.0.3Compare Source
v8.0.2Compare Source
v8.0.1Compare Source
karma-runner/karma-chrome-launcher (karma-chrome-launcher)
v3.2.0Compare Source
Features
3.1.1 (2022-03-09)
Bug Fixes
v3.1.1Compare Source
Bug Fixes
v3.1.0Compare Source
Features
v3.0.0Compare Source
Features
karma-runner/karma-coverage (karma-coverage)
v2.2.1Compare Source
Bug Fixes
v2.2.0Compare Source
Features
2.1.1 (2022-02-05)
Bug Fixes
v2.1.1Compare Source
Bug Fixes
v2.1.0Compare Source
Bug Fixes
Features
2.0.3 (2020-07-24)
Bug Fixes
2.0.2 (2020-04-13)
Bug Fixes
2.0.1 (2019-08-20)
v2.0.3Compare Source
Bug Fixes
v2.0.2Compare Source
Bug Fixes
v2.0.1Compare Source
2.0.1 (2019-08-20)
v2.0.0Compare Source
Bug Fixes
Chores
BREAKING CHANGES
deps: This set of changes may impact some use cases.
chore: Add Updated Istanbul Dependencies
The istanbul package is deprecated in favor several split packages that
control different aspects of how istanbul works. This commit adds the
recommended packages that will be used in future commits as
karma-coverage's usage of istanbul is updated to the latest api.
This commit refactors the in memory report implementation to use the new
istanbul report API.
Report creation is removed from newer versions of the istanbul API, so
this commit adds a set of utility functions to wrap around the new API
and provide similar functionality as the old API. The top level export
uses the new utility function to register the in-memory report.
This commit updates the preprocessor to use istanbul-lib-instrument
instead of the deprecated istanbul package. The biggest change in this
refactor is using a callable function instead of a constructor when
creating instrumenters
The old istanbul package exposed the Instrumenter directly, allowing the
preprocessor to create an instance of it. istanbul-lib-instrument,
however, exposes a callable function that creates an Instrumenter.
This commit updates the preprocessor to follow this new pattern of using
a callable function. In order to ensure backwards compatibility, a
utility function is added to wrap constructors with a callable function
for creation automatically.
This change allows the following configuration for creating instrumenters:
This commit also uses the istanbul-lib-source-maps package to handle
storing source maps. A global source map store registers source maps so
they can be used later on in the reporter.
This commit updates the reporter by using the istanbul-lib-coverage
package api for handling coverage checking/management and the
istanbul-lib-report package api for handling reporting.
The new apis remove the need for collectors and remove the need to
handle disposing collectors.
This commit removes the source-cache-store and source-cache files as
they are no longer being used. The source-map-store and
istanbul-lib-source-maps are used instead, so these files are no longer
needed.
This commit updates the report creator utility to allow resetting the
custom reporter map.
This commit updates the preprocessor to properly access file coverage
when storing it in the global coverage map (when includeAllSources is
true). The previous method did not work because the returned
instrumented code from the default istanbul instrumenter returns the
coverage map in a POJO object instead of JSON notation. This breaks the
coverage regex used to match and parse the coverage map.
The istanbul instrumenter offers the ability to receive the coverage map
for the last instrumented file through a separate function, so that is
tested for and used if it is supported. The original method is used as a
fallback for backwards compatibility.
This commit also addresses changes from the v0 instanbul instrumenter
options. The changes are additive only to maintain backwards compatibility
for other instrumenters.
This commit fixes errors with accessing data properly during the
checkCoverage method. A previous commit updated the implementation to
use istanbul-lib-coverage, but this involved an api change to access the
raw coverage data (which checkCoverage uses).
This commit also fixes the checking coverage for each file by using a
map to store file coverage summaries instead of merging summaries like
the global results. Per file coverage now works as expected.
This commit updates the mocking done in unit tests to properly mock the
new istanbul API. Additionally, new unit test suites are added for the
utility methods report-creator and source-map-store.
:1.1.2 (2018-05-03)
Bug Fixes
BREAKING CHANGES
:1.1.1 (2016-07-23)
Bug Fixes
karma-runner/karma-firefox-launcher (karma-firefox-launcher)
v2.1.3Compare Source
v2.1.2Compare Source
Bug Fixes
v2.1.1Compare Source
Bug Fixes
v2.1.0Compare Source
Features
v2.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
Node 8 EOL was 2019-12-31.
v1.3.0Compare Source
Bug Fixes
karma-runner/karma-mocha (karma-mocha)
v2.0.1Compare Source
Bug Fixes
v2.0.0Compare Source
Features
ci: enable semanitic-release (5a5b6d5)
Expose 'pending' status (e847121), closes #109
Update Node.js versions (fd64f5b)
BREAKING CHANGES
mochajs/mocha (mocha)
v10.4.0Compare Source
🎉 Enhancements
.causestacks in the error stack traces (@voxpelli)🐛 Fixes
lib/cli/run.js(@stalet)🔩 Other
v10.3.0Compare Source
This is a stable release equivalent to 10.30.0-prerelease.
v10.2.0Compare Source
🎉 Enhancements
🐛 Fixes
📖 Documentation
v10.1.0Compare Source
🎉 Enhancements
prefers-color-scheme: dark(@greggman)🔩 Other
Promise.allSettledinstead of polyfill (@outsideris)clean(@yetingli)v10.0.0Compare Source
💥 Breaking Changes
#4845: Drop Node.js v12.x support (@juergba)
#4848: Drop Internet-Explorer-11 support (@juergba)
#4857: Drop AMD/RequireJS support (@juergba)
#4866: Drop Growl notification support (@juergba)
#4863: Rename executable
bin/mochatobin/mocha.js(@juergba)#4865:
--ignoreoption in Windows: upgrade Minimatch (@juergba)#4861: Remove deprecated
Runnersignature (@juergba)🔩 Other
#4878: Update production dependencies (@juergba)
#4876: Add Node.js v18 to CI test matrix (@outsideris)
#4852: Replace deprecated
String.prototype.substr()(@CommanderRoot)Also thanks to @ea2305 and @SukkaW for improvements to our documentation.
v9.2.2Compare Source
🐛 Fixes
#4842: Loading of reporter throws wrong error (@juergba)
#4839:
dry-run: prevent potential call-stack crash (@juergba)🔩 Other
v9.2.1Compare Source
🐛 Fixes
#4832: Loading of config files throws wrong error (@juergba)
#4799: Reporter: configurable
maxDiffSizereporter-option (@norla)v9.2.0Compare Source
🎉 Enhancements
🔩 Other
v9.1.4Compare Source
🐛 Fixes
importthrows wrong error if loader is used (@giltayar)🔩 Other
v9.1.3Compare Source
🐛 Fixes
bddES6 style import (@juergba)🔩 Other
EVENT_SUITE_ADD_*events (@beatfactor)v9.1.2Compare Source
🐛 Fixes
browser-entry.js(@PaperStrike)🔩 Other
v9.1.1Compare Source
🐛 Fixes
XUNITandJSONreporter crash inparallelmode (@curtisman)v9.1.0Compare Source
🎉 Enhancements
--fail-zero(@juergba)--node-option(@juergba)JSONreporter (@dorny)v9.0.3Compare Source
🐛 Fixes
#4702: Error rethrow from cwd-relative path while loading
.mocharc.js(@kirill-golovan)#4688: Usage of custom interface in parallel mode (@juergba)
#4687: ESM: don't swallow
MODULE_NOT_FOUNDerrors in case oftype:module(@giltayar)v9.0.2Compare Source
🐛 Fixes
--require <dir>work with newimport-first loading (@giltayar)🔩 Other
v9.0.1Compare Source
🔩 Other
We added a separate browser bundle
mocha-es2018.jsin javascript ES2018, as we skipped the transpilation down to ES5. This is an experimental step towards freezing Mocha's support of IE11.hasStableEsmImplementation(@alexander-fenster)v9.0.0Compare 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, asimportcan also load most files thatrequiredoes. 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/expectedfordiffgeneration (@juergba)#4389: Refactoring: Consuming log-symbols alternate to code for win32 in reporters/base (@MoonSupport)
🎉 Enhancements
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 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 Mend Renovate. View repository job log here.