-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update all (major) #8
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
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
c1be7e3
to
5913a36
Compare
641558f
to
bede3e2
Compare
bede3e2
to
6834b09
Compare
565687e
to
bdd9f11
Compare
bdd9f11
to
9536983
Compare
eb90118
to
2fafb6a
Compare
bd01d23
to
baab0b8
Compare
960fb75
to
362a765
Compare
1d6f7b4
to
a57ce0a
Compare
539919b
to
4bb09e1
Compare
8fe7c9c
to
664553f
Compare
664553f
to
15a77c5
Compare
15a77c5
to
31db70b
Compare
b5c5404
to
ee59ca3
Compare
8aa54da
to
3779c9a
Compare
b4f445a
to
4a38097
Compare
737be45
to
02f63d9
Compare
02f63d9
to
a2ea3ca
Compare
a2ea3ca
to
9880605
Compare
9880605
to
3851152
Compare
3851152
to
af12c6e
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.2
v4.0.2+incompatible
->v5.2.1
0.7.20
->10.9.2
2.2.0
->3.2.0
1.1.2
->2.2.1
1.2.0
->2.1.3
1.3.0
->2.0.1
1.21.5
->11.1.0
2.3.1
->4.0.0
2.8.29
->3.19.3
Release Notes
kurttheviking/git-rev-sync-js (git-rev-sync)
v3.0.2
Compare Source
v3.0.1
Compare Source
v3.0.0
Compare Source
v2.1.0
Compare Source
v2.0.0
Compare Source
go-chi/chi (github.com/go-chi/chi)
v5.2.1
Compare Source
Starting this release, we will now support the four most recent major versions of Go. See https://github.com/go-chi/chi/issues/963 for related discussion.
What's Changed
Full Changelog: go-chi/chi@v5.2.0...v5.2.1
v5.2.0
Compare Source
What's Changed
Find
toRoutes
interface by @joeriddles in https://github.com/go-chi/chi/pull/872_examples/versions
by @hongkuancn in https://github.com/go-chi/chi/pull/948Mux.Find
not correctly handling nested routes by @joeriddles in https://github.com/go-chi/chi/pull/954New Contributors
Full Changelog: go-chi/chi@v5.1.0...v5.2.0
v5.1.0
Compare Source
What's Changed
Discard()
method to themiddleware.WrapResponseWriter
interface. This is technically an API breaking change. However after some discussion at https://github.com/go-chi/chi/pull/926#discussion_r1658333481, we decided to move forward, and release as minor version, as we don't expect anyone to rely on this interface / implement it externally.New Contributors
Full Changelog: go-chi/chi@v5.0.14...v5.1.0
v5.0.14
Compare Source
v5.0.13
Compare Source
What's Changed
New Contributors
Full Changelog: go-chi/chi@v5.0.12...v5.0.13
v5.0.12
Compare Source
v5.0.11
Compare Source
v5.0.10
Compare Source
v5.0.9
Compare Source
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
github.com/go-chi/chi/v5
introduces 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.3
Compare Source
v4.1.2
Compare Source
v4.1.2+incompatible
Compare Source
v4.1.1
Compare Source
route to the correct handler through a recursive tree search, thanks to @Jahaja for the PR/fix!
v4.1.1+incompatible
Compare Source
v4.1.0
Compare Source
and an extra interface type useful for custom logger implementations.
v4.1.0+incompatible
Compare Source
v4.0.4
Compare Source
v4.0.4+incompatible
Compare Source
v4.0.3
Compare Source
v4.0.3+incompatible
Compare Source
jakejs/jake (jake)
v10.9.2
Compare Source
v10.9.1
Compare Source
v10.8.7
Compare Source
v10.8.6
Compare Source
v10.8.5
Compare Source
v10.8.2
Compare Source
v10.8.1
Compare Source
v10.7.1
Compare Source
v10.6.1
Compare Source
v10.5.2
Compare Source
v10.4.7
Compare Source
v10.4.6
Compare Source
v10.4.5
Compare Source
v10.4.4
Compare Source
v10.4.3
Compare Source
v10.4.2
Compare Source
v10.4.1
Compare Source
v10.3.2
Compare Source
v10.3.1
Compare Source
v10.3.0
Compare Source
v10.1.11
Compare Source
v10.1.10
Compare Source
v10.1.9
Compare Source
v10.1.7
Compare Source
v10.1.6
Compare Source
v10.1.5
Compare Source
v10.1.4
Compare Source
v10.1.3
Compare Source
v10.1.2
Compare Source
v10.1.1
Compare Source
v10.0.6
Compare Source
v10.0.3
Compare Source
v10.0.2
Compare Source
v8.1.1
Compare Source
v8.0.19
Compare Source
v8.0.18
Compare Source
v8.0.16
Compare Source
v8.0.15
Compare Source
v8.0.14
Compare Source
v8.0.12
Compare Source
v8.0.11
Compare Source
v8.0.10
Compare Source
v8.0.9
Compare Source
v8.0.8
Compare Source
v8.0.6
Compare Source
v8.0.5
Compare Source
v8.0.4
Compare Source
v8.0.3
Compare Source
v8.0.2
Compare Source
v8.0.1
Compare Source
karma-runner/karma-chrome-launcher (karma-chrome-launcher)
v3.2.0
Compare Source
Features
3.1.1 (2022-03-09)
Bug Fixes
v3.1.1
Compare Source
Bug Fixes
v3.1.0
Compare Source
Features
v3.0.0
Compare Source
Features
karma-runner/karma-coverage (karma-coverage)
v2.2.1
Compare Source
Bug Fixes
v2.2.0
Compare Source
Features
2.1.1 (2022-02-05)
Bug Fixes
v2.1.1
Compare Source
Bug Fixes
v2.1.0
Compare 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.3
Compare Source
Bug Fixes
v2.0.2
Compare Source
Bug Fixes
v2.0.1
Compare Source
2.0.1 (2019-08-20)
v2.0.0
Compare 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.3
Compare Source
v2.1.2
Compare Source
Bug Fixes
v2.1.1
Compare Source
Bug Fixes
v2.1.0
Compare Source
Features
v2.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
Node 8 EOL was 2019-12-31.
v1.3.0
Compare Source
Bug Fixes
karma-runner/karma-mocha (karma-mocha)
v2.0.1
Compare Source
Bug Fixes
v2.0.0
Compare Source
Features
ci: enable semanitic-release (5a5b6d5)
Expose 'pending' status (e847121), closes #109
Update Node.js versions (fd64f5b)
BREAKING CHANGES
mochajs/mocha (mocha)
v11.1.0
Compare Source
🌟 Features
strip-ansi
withutil.stripVTControlCharacters
(#5267) (3c191c0), closes #5265v11.0.2
Compare Source
🩹 Fixes
📚 Documentation
status: accepting prs
link (#5268) (f729cd0)v11.0.1
Compare Source
🌟 Features
📚 Documentation
linkPartialObjects
methods (#5255) (34e0e52)v11.0.0
Compare Source
⚠ BREAKING CHANGES
🌟 Features
🩹 Fixes
📚 Documentation
v10.8.2
Compare Source
🩹 Fixes
📚 Documentation
🧹 Chores
🤖 Automation
v10.8.1
Compare Source
🩹 Fixes
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 was generated by Mend Renovate. View the repository job log.