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

chore(deps): update dependency karma to v6 [security] #92

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 7, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
karma (source) 1.7.1 -> 6.3.16 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2022-0437

karma prior to version 6.3.14 contains a cross-site scripting vulnerability.

CVE-2021-23495

Karma before 6.3.16 is vulnerable to Open Redirect due to missing validation of the return_url query parameter.


Release Notes

karma-runner/karma (karma)

v6.3.16

Compare Source

Bug Fixes
  • security: mitigate the "Open Redirect Vulnerability" (ff7edbb)

v6.3.15

Compare Source

Bug Fixes

v6.3.14

Compare Source

Bug Fixes
  • remove string template from client code (91d5acd)
  • warn when singleRun and autoWatch are false (69cfc76)
  • security: remove XSS vulnerability in returnUrl query param (839578c)

v6.3.13

Compare Source

Bug Fixes

v6.3.12

Compare Source

Bug Fixes
  • remove depreciation warning from log4js (41bed33)

v6.3.11

Compare Source

Bug Fixes
  • deps: pin colors package to 1.4.0 due to security vulnerability (a5219c5)

v6.3.10

Compare Source

Bug Fixes
  • logger: create parent folders if they are missing (0d24bd9), closes #​3734

v6.3.9

Compare Source

Bug Fixes

v6.3.8

Compare Source

Bug Fixes
  • reporter: warning if stack trace contains generated code invocation (4f23b14)

v6.3.7

Compare Source

Bug Fixes
  • middleware: replace %X_UA_COMPATIBLE% marker anywhere in the file (f1aeaec), closes #​3711

v6.3.6

Compare Source

Bug Fixes

v6.3.5

Compare Source

Bug Fixes
  • client: prevent socket.io from hanging due to mocked clocks (#​3695) (105da90)

v6.3.4

Compare Source

Bug Fixes

v6.3.3

Compare Source

Bug Fixes

v6.3.2

Compare Source

Bug Fixes

v6.3.1

Compare Source

Bug Fixes
  • client: error out when opening a new tab fails (099b85e)

v6.3.0

Compare Source

Features
  • support asynchronous config.set() call in karma.conf.js (#​3660) (4c9097a)

v6.2.0

Compare Source

Features
  • plugins: add support wildcard config for scoped package plugin (#​3659) (39831b1)

6.1.2 (2021-03-09)

Bug Fixes

6.1.1 (2021-02-12)

Bug Fixes

v6.1.2

Compare Source

Bug Fixes

v6.1.1

Compare Source

Bug Fixes

v6.1.0

Compare Source

Features
  • config: improve karma.config.parseConfig error handling (#​3635) (9dba1e2)

6.0.4 (2021-02-01)

Bug Fixes

6.0.3 (2021-01-27)

Bug Fixes
  • plugins: refactor instantiatePlugin from preproprocessor (#​3628) (e02858a)

6.0.2 (2021-01-25)

Bug Fixes

6.0.1 (2021-01-20)

Bug Fixes

v6.0.4

Compare Source

Bug Fixes

v6.0.3

Compare Source

Bug Fixes
  • plugins: refactor instantiatePlugin from preproprocessor (#​3628) (e02858a)

v6.0.2

Compare Source

Bug Fixes

v6.0.1

Compare Source

Bug Fixes

v6.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES
  • server: Deprecated require('karma').server.start() and require('karma').Server.start() variants were removed from the public API. Instead use canonical form:
const { Server } = require('karma');
const server = new Server();
server.start();
  • cli: Karma is more strict and will error out if unknown option or argument is passed to CLI.
  • Using Karma to run Dart code in the browser is no longer supported. Use your favorite Dart-to-JS compiler instead.

dart file type has been removed without a replacement.

customFileHandlers DI token has been removed. Use middleware to achieve similar functionality.

customScriptTypes DI token has been removed. It had no effect, so no replacement is provided.

  • deps: Some projects have socket.io tests that are version sensitive.

5.2.3 (2020-09-25)

Bug Fixes

5.2.2 (2020-09-08)

Bug Fixes

5.2.1 (2020-09-02)

Bug Fixes

v5.2.3

Compare Source

Bug Fixes

v5.2.2

Compare Source

Bug Fixes

v5.2.1

Compare Source

Bug Fixes

v5.2.0

Compare Source

Bug Fixes
Features

5.1.1 (2020-07-28)

Bug Fixes

v5.1.1

Compare Source

Bug Fixes

v5.1.0

Compare Source

Features

5.0.9 (2020-05-19)

Bug Fixes

5.0.8 (2020-05-18)

Bug Fixes

5.0.7 (2020-05-16)

Bug Fixes

5.0.6 (2020-05-16)

Bug Fixes

5.0.5 (2020-05-07)

Bug Fixes

5.0.4 (2020-04-30)

Bug Fixes
  • browser: make sure that empty results array is still recognized (#​3486) (fa95fa3)

5.0.3 (2020-04-29)

Bug Fixes

5.0.2 (2020-04-16)

Bug Fixes

5.0.1 (2020-04-10)

Bug Fixes

v5.0.9

Compare Source

Bug Fixes

v5.0.8

Compare Source

Bug Fixes

v5.0.7

Compare Source

Bug Fixes

v5.0.6

Compare Source

Bug Fixes

v5.0.5

Compare Source

Bug Fixes

v5.0.4

Compare Source

Bug Fixes
  • browser: make sure that empty results array is still recognized (#​3486) (fa95fa3)

v5.0.3

Compare Source

Bug Fixes

v5.0.2

Compare Source

Bug Fixes

v5.0.1

Compare Source

Bug Fixes

v5.0.0

Compare Source

Bug Fixes
Code Refactoring
Continuous Integration
Features
BREAKING CHANGES
  • Karma plugins which rely on the fact that Karma uses Bluebird promises may break as Bluebird-specific API is no longer available on Promises returned by the Karma core
  • server: Deprecated createPreprocessor removed, karma-browserify < 7 version doesn't work
  • no more testing on node 8.

4.4.1 (2019-10-18)

Bug Fixes
  • deps: back to karma-browserstack-launcher 1.4 (#​3361) (1cd87ad)
  • server: Add test coverage for config.singleRun true branch. (#​3384) (259be0d)
  • if preprocessor is async function and doesn't return a content then await donePromise (#​3387) (f91be24)

v4.4.1

Compare Source

Bug Fixes
  • deps: back to karma-browserstack-launcher 1.4 (#​3361) (1cd87ad)
  • server: Add test coverage for config.singleRun true branch. (#​3384) (259be0d)
  • if preprocessor is async function and doesn't return a content then await donePromise (#​3387) (f91be24)

v4.4.0

Compare Source

Bug Fixes
Features

v4.3.0

Compare Source

Bug Fixes
Features

v4.2.0

Compare Source

Bug Fixes

v4.1.0

Compare Source

Bug Fixes

4.0.1 (2019-02-28)

Bug Fixes

v4.0.1

Compare Source

Bug Fixes

v4.0.0

Compare Source

Bug Fixes
Chores
BREAKING CHANGES
  • Drop Support for Node 6, to make it possible to use async/await in karma codebase.

3.1.4 (2018-12-17)

Bug Fixes

3.1.3 (2018-12-01)

Bug Fixes

3.1.2 (2018-12-01)

Bug Fixes
Features

3.1.1 (2018-10-23)

Bug Fixes

v3.1.4

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - "" (UTC), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

@renovate renovate bot changed the title Update dependency karma to v6 [SECURITY] Update dependency karma to v6 [SECURITY] - autoclosed Mar 11, 2023
@renovate renovate bot closed this Mar 11, 2023
@renovate renovate bot deleted the renovate/npm-karma-vulnerability branch March 11, 2023 03:57
@renovate renovate bot changed the title Update dependency karma to v6 [SECURITY] - autoclosed Update dependency karma to v6 [SECURITY] Mar 11, 2023
@renovate renovate bot reopened this Mar 11, 2023
@renovate renovate bot restored the renovate/npm-karma-vulnerability branch March 11, 2023 07:06
@renovate renovate bot force-pushed the renovate/npm-karma-vulnerability branch from 5f0ea40 to 27406f4 Compare March 11, 2023 09:51
@renovate renovate bot changed the title Update dependency karma to v6 [SECURITY] chore(deps): update dependency karma to 6.3.16 [security] Mar 11, 2023
@renovate
Copy link
Author

renovate bot commented Mar 11, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @ngrx/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/rxjs
npm ERR!   rxjs@"6.5.4" from the root project
npm ERR!   rxjs@"6.5.4" from @angular-devkit/[email protected]
npm ERR!   node_modules/@angular-devkit/schematics
npm ERR!     @angular-devkit/schematics@"9.1.7" from @angular/[email protected]
npm ERR!     node_modules/@angular/cli
npm ERR!       dev @angular/cli@"^9.0.4" from the root project
npm ERR!     @angular-devkit/schematics@"9.1.7" from @schematics/[email protected]
npm ERR!     node_modules/@schematics/angular
npm ERR!       @schematics/angular@"9.1.7" from @angular/[email protected]
npm ERR!       node_modules/@angular/cli
npm ERR!         dev @angular/cli@"^9.0.4" from the root project
npm ERR!     1 more (@schematics/update)
npm ERR!   20 more (@angular-devkit/core, @angular-devkit/architect, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer rxjs@"^5.0.0-beta.12" from @ngrx/[email protected]
npm ERR! node_modules/@ngrx/core
npm ERR!   @ngrx/core@"^1.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/rxjs
npm ERR!   peer rxjs@"^5.0.0-beta.12" from @ngrx/[email protected]
npm ERR!   node_modules/@ngrx/core
npm ERR!     @ngrx/core@"^1.2.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2023-03-11T09_51_39_926Z-debug-0.log

@renovate renovate bot changed the title chore(deps): update dependency karma to 6.3.16 [security] chore(deps): update dependency karma to v6 [security] Mar 24, 2023
@renovate renovate bot changed the title chore(deps): update dependency karma to v6 [security] chore(deps): update dependency karma to v6 [security] - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/npm-karma-vulnerability branch December 8, 2024 18:32
@renovate renovate bot changed the title chore(deps): update dependency karma to v6 [security] - autoclosed chore(deps): update dependency karma to v6 [security] Dec 8, 2024
@renovate renovate bot reopened this Dec 8, 2024
@renovate renovate bot force-pushed the renovate/npm-karma-vulnerability branch from ec8707d to 27406f4 Compare December 8, 2024 23:06
Copy link
Author

renovate bot commented Dec 8, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @ngrx/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/rxjs
npm ERR!   rxjs@"6.5.4" from the root project
npm ERR!   rxjs@"6.5.4" from @angular-devkit/[email protected]
npm ERR!   node_modules/@angular-devkit/schematics
npm ERR!     @angular-devkit/schematics@"9.1.7" from @angular/[email protected]
npm ERR!     node_modules/@angular/cli
npm ERR!       dev @angular/cli@"^9.0.4" from the root project
npm ERR!     @angular-devkit/schematics@"9.1.7" from @schematics/[email protected]
npm ERR!     node_modules/@schematics/angular
npm ERR!       @schematics/angular@"9.1.7" from @angular/[email protected]
npm ERR!       node_modules/@angular/cli
npm ERR!         dev @angular/cli@"^9.0.4" from the root project
npm ERR!     1 more (@schematics/update)
npm ERR!   20 more (@angular-devkit/core, @angular-devkit/architect, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer rxjs@"^5.0.0-beta.12" from @ngrx/[email protected]
npm ERR! node_modules/@ngrx/core
npm ERR!   @ngrx/core@"^1.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/rxjs
npm ERR!   peer rxjs@"^5.0.0-beta.12" from @ngrx/[email protected]
npm ERR!   node_modules/@ngrx/core
npm ERR!     @ngrx/core@"^1.2.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-12-08T23_06_13_741Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants