Skip to content
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
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 9, 2019

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
git-rev-sync 1.12.0 -> 3.0.2 age adoption passing confidence
github.com/go-chi/chi v4.0.2+incompatible -> v5.2.1 age adoption passing confidence
jake 0.7.20 -> 10.9.2 age adoption passing confidence
karma-chrome-launcher 2.2.0 -> 3.2.0 age adoption passing confidence
karma-coverage 1.1.2 -> 2.2.1 age adoption passing confidence
karma-firefox-launcher 1.2.0 -> 2.1.3 age adoption passing confidence
karma-mocha 1.3.0 -> 2.0.1 age adoption passing confidence
mocha (source) 1.21.5 -> 11.1.0 age adoption passing confidence
rollup-plugin-json 2.3.1 -> 4.0.0 age adoption passing confidence
uglify-js 2.8.29 -> 3.19.3 age adoption passing confidence

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

⚠️ Chi supports Go 1.20+

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

New Contributors

Full Changelog: go-chi/chi@v5.1.0...v5.2.0

v5.1.0

Compare Source

What's Changed

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

  • chi v5, github.com/go-chi/chi/v5 introduces the adoption of Go's SIV to adhere to the current state-of-the-tools in Go.
  • chi v1.5.x did not work out as planned, as the Go tooling is too powerful and chi's adoption is too wide.
    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 seeking
    will still come to fruition in some form, https://github.com/golang/go/issues/445504550
  • History of changes: see go-chi/chi@v1.5.4...v5.0.0

v4.1.3

Compare Source

v4.1.2

Compare Source

v4.1.2+incompatible

Compare Source

v4.1.1

Compare Source

v4.1.1+incompatible

Compare Source

v4.1.0

Compare Source

  • middleware.LogEntry: Write method on interface now passes the response header
    and an extra interface type useful for custom logger implementations.
  • middleware.WrapResponseWriter: minor fix
  • middleware.Recoverer: a bit prettier
  • History of changes: see go-chi/chi@v4.0.4...v4.1.0

v4.1.0+incompatible

Compare Source

v4.0.4

Compare Source

v4.0.4+incompatible

Compare Source

v4.0.3

Compare Source

  • core: fix regexp routing to include default value when param is not matched
  • middleware: rewrite of middleware.Compress
  • middleware: suppress http.ErrAbortHandler in middleware.Recoverer
  • History of changes: see go-chi/chi@v4.0.2...v4.0.3

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
  • add process.env.ProgramW6432 as root location for binaries (12a73db)

3.1.1 (2022-03-09)

Bug Fixes
  • artificially trigger a release (83fdc3c)

v3.1.1

Compare Source

Bug Fixes
  • artificially trigger a release (83fdc3c)

v3.1.0

Compare Source

Features
  • add --disable-dev-shm-usage flag to headless (137005d)

v3.0.0

Compare Source

Features
  • allow overriding of the default debug port (26ae9f4), closes #​187
karma-runner/karma-coverage (karma-coverage)

v2.2.1

Compare Source

Bug Fixes
  • exit code when reporter file is not provided (1388186)

v2.2.0

Compare Source

Features
  • update Istanbul packages (24aac11)

2.1.1 (2022-02-05)

Bug Fixes

v2.1.1

Compare Source

Bug Fixes

v2.1.0

Compare Source

Bug Fixes
  • deps: update main and dev dependencies (c20d982)
Features
  • reporter: log coverage threshold as a warning fixed #​432 (a6c95d8)

2.0.3 (2020-07-24)

Bug Fixes
  • report: waiting promise resolve in onExist method fix #​418 (c93f061)

2.0.2 (2020-04-13)

Bug Fixes

2.0.1 (2019-08-20)

v2.0.3

Compare Source

Bug Fixes
  • report: waiting promise resolve in onExist method fix #​418 (c93f061)

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.

  • refactor(reporter): Follow new report 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.

  • refactor(preprocessor): Switch to istanbul-lib-instrument

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:

  1. An object that contains an Instrumenter constructor
  2. An Instrumenter constructor itself
  3. A callable function that returns an Instrumenter instance.

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.

  • refactor(reporter): Switch to istanbul-lib-coverage

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.

  • refactor: Remove unused source cache utilities

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.

  • feat(util): Add Reset Functionality

This commit updates the report creator utility to allow resetting the
custom reporter map.

  • fix(preprocessor): Track Coverage Maps Properly

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.

  • fix(reporter): Access Data Properly to Check Coverage

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.

  • test: Update Unit Tests to use new Istanbul API

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.

  • drop support for node < 8
  • reporter: the output folder names change, they no longer contain :

1.1.2 (2018-05-03)

Bug Fixes
  • build: Update to lodash 4 (d6d21d2), closes #​242
  • reporter: replace colons in the output path (3b2bffa)
BREAKING CHANGES
  • reporter: the output folder names change, they no longer contain :

1.1.1 (2016-07-23)

Bug Fixes
  • remove usage of the deprecated helper._ (dacf9e9)
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
  • update name of Developer Edition on macOS (a0b5e58)

v2.1.0

Compare Source

Features
  • provide a way to configure location of executable in customLauncher (fix #​125) (c53efcc)

v2.0.0

Compare Source

Bug Fixes
  • Bypass WSL check if Firefox is present in WSL environment (23a5d10), closes #​107
  • Update is-wsl to v2.2.0 to detect docker under WSL (#​116) (c585393)
Features
BREAKING CHANGES
  • Changed minimum required version of node.js from 8 to 10.

Node 8 EOL was 2019-12-31.

v1.3.0

Compare Source

Bug Fixes
  • Check that wsl path exists before using wslpath to convert it (#​105) (1eb7e1b)
karma-runner/karma-mocha (karma-mocha)

v2.0.1

Compare Source

Bug Fixes
  • deps: Report fails without emit 'test end' event (#​223) (1a8226c)

v2.0.0

Compare Source

Features
BREAKING CHANGES
  • drop support for node 8
mochajs/mocha (mocha)

v11.1.0

Compare Source

🌟 Features

v11.0.2

Compare Source

🩹 Fixes
  • catch exceptions setting Error.stackTraceLimit (#​5254) (259f8f8)
  • error handling for unexpected numeric arguments passed to cli (#​5263) (210d658)
📚 Documentation

v11.0.1

Compare Source

🌟 Features
📚 Documentation

v11.0.0

Compare Source

⚠ BREAKING CHANGES
  • adapt new engine range for Mocha 11 (#​5216)
🌟 Features
🩹 Fixes
📚 Documentation

v10.8.2

Compare Source

🩹 Fixes
📚 Documentation
  • indicate 'exports' interface does not work in browsers (#​5181) (14e640e)
🧹 Chores
  • fix docs builds by re-adding eleventy and ignoring gitignore again (#​5240) (881e3b0)
🤖 Automation

v10.8.1

Compare Source

🩹 Fixes
  • handle case of invalid package.j

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.


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

This PR was generated by Mend Renovate. View the repository job log.

@trafico-bot trafico-bot bot added the 🔍 Ready for Review Pull Request is not reviewed yet label Aug 9, 2019
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from c1be7e3 to 5913a36 Compare August 13, 2019 22:41
@renovate renovate bot force-pushed the renovate/major-all branch 6 times, most recently from 641558f to bede3e2 Compare August 27, 2019 15:49
@renovate renovate bot force-pushed the renovate/major-all branch from bede3e2 to 6834b09 Compare August 28, 2019 12:10
@renovate renovate bot force-pushed the renovate/major-all branch 4 times, most recently from 565687e to bdd9f11 Compare September 14, 2019 17:45
@renovate renovate bot force-pushed the renovate/major-all branch from bdd9f11 to 9536983 Compare September 16, 2019 10:39
@renovate renovate bot force-pushed the renovate/major-all branch 4 times, most recently from eb90118 to 2fafb6a Compare October 5, 2019 06:15
@renovate renovate bot force-pushed the renovate/major-all branch 4 times, most recently from bd01d23 to baab0b8 Compare October 15, 2019 06:02
@renovate renovate bot force-pushed the renovate/major-all branch 6 times, most recently from 960fb75 to 362a765 Compare October 18, 2019 20:23
@renovate renovate bot force-pushed the renovate/major-all branch 4 times, most recently from 1d6f7b4 to a57ce0a Compare July 20, 2024 21:01
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from 539919b to 4bb09e1 Compare August 1, 2024 10:02
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 8fe7c9c to 664553f Compare August 9, 2024 14:10
@renovate renovate bot force-pushed the renovate/major-all branch from 664553f to 15a77c5 Compare August 10, 2024 13:12
@renovate renovate bot force-pushed the renovate/major-all branch from 15a77c5 to 31db70b Compare August 18, 2024 06:57
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from b5c5404 to ee59ca3 Compare August 30, 2024 09:25
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 8aa54da to 3779c9a Compare September 19, 2024 07:47
@renovate renovate bot force-pushed the renovate/major-all branch 6 times, most recently from b4f445a to 4a38097 Compare September 27, 2024 01:42
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 737be45 to 02f63d9 Compare October 30, 2024 20:32
@renovate renovate bot force-pushed the renovate/major-all branch from 02f63d9 to a2ea3ca Compare December 2, 2024 18:14
@renovate renovate bot changed the title chore(deps): update all (major) fix(deps): update all (major) Dec 10, 2024
@renovate renovate bot force-pushed the renovate/major-all branch from a2ea3ca to 9880605 Compare December 15, 2024 22:06
@renovate renovate bot force-pushed the renovate/major-all branch from 9880605 to 3851152 Compare January 22, 2025 17:12
@renovate renovate bot force-pushed the renovate/major-all branch from 3851152 to af12c6e Compare February 4, 2025 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔍 Ready for Review Pull Request is not reviewed yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants