Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented May 28, 2023

This PR contains the following updates:

Package Change Age Confidence
jasmine-core (source) ~4.5.0 -> ~5.12.0 age confidence

Release Notes

jasmine/jasmine (jasmine-core)

v5.12.0

Compare Source

Please see the release notes.

v5.11.0

Compare Source

Please see the release notes.

v5.10.0

Compare Source

Please see the release notes.

v5.9.0

Compare Source

Please see the release notes.

v5.8.0

Compare Source

Please see the release notes.

v5.7.1

Compare Source

Please see the release notes.

v5.7.0

Compare Source

Please see the release notes.

v5.6.0

Compare Source

Please see the release notes.

v5.5.0

Compare Source

Please see the release notes.

v5.4.0

Compare Source

Please see the release notes.

v5.3.0

Compare Source

Please see the release notes.

v5.2.0

Compare Source

Please see the release notes.

v5.1.2: 5.1.2

Compare Source

Please see the release notes.

v5.1.1: 5.1.1

Compare Source

Please see the release notes.

v5.1.0: 5.1.0

Compare Source

Please see the release notes.

v5.0.1: 5.0.1

Compare Source

Please see the release notes.

v5.0.0: 5.0.0

Compare Source

Please see the release notes.

v4.6.1: 4.6.1

Compare Source

Please see the release notes.

v4.6.0: 4.6.0

Compare Source

Please see the release notes.


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.

@renovate
Copy link
Author

renovate bot commented May 28, 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
/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jasmine-core
npm ERR!   dev jasmine-core@"~5.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jasmine-core@"^4.0.0" from [email protected]
npm ERR! node_modules/karma-jasmine-html-reporter
npm ERR!   dev karma-jasmine-html-reporter@"~2.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/jasmine-core
npm ERR!   peer jasmine-core@"^4.0.0" from [email protected]
npm ERR!   node_modules/karma-jasmine-html-reporter
npm ERR!     dev karma-jasmine-html-reporter@"~2.0.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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/eb49aa/3b8ef6/cache/others/npm/_logs/2023-07-23T05_19_55_456Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/eb49aa/3b8ef6/cache/others/npm/_logs/2023-07-23T05_19_55_456Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from 7b44495 to 8c7b5e8 Compare July 23, 2023 05:20
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from 8c7b5e8 to e22d53a Compare July 21, 2024 17:53
@renovate
Copy link
Author

renovate bot commented Jul 21, 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/jasmine-core
npm error   dev jasmine-core@"~5.12.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jasmine-core@"^4.0.0" from [email protected]
npm error node_modules/karma-jasmine-html-reporter
npm error   dev karma-jasmine-html-reporter@"~2.0.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/jasmine-core
npm error   peer jasmine-core@"^4.0.0" from [email protected]
npm error   node_modules/karma-jasmine-html-reporter
npm error     dev karma-jasmine-html-reporter@"~2.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-10-25T03_55_15_862Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-25T03_55_15_862Z-debug-0.log

@sonarqubecloud
Copy link

@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from e22d53a to f2624f7 Compare September 8, 2024 02:53
@sonarqubecloud
Copy link

sonarqubecloud bot commented Sep 8, 2024

@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from f2624f7 to ffc072e Compare October 13, 2024 02:59
@sonarqubecloud
Copy link

@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from ffc072e to 7a96e5e Compare December 4, 2024 23:43
@sonarqubecloud
Copy link

sonarqubecloud bot commented Dec 4, 2024

@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from 7a96e5e to 672a890 Compare February 9, 2025 06:58
@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from 672a890 to ba5566e Compare April 27, 2025 04:14
@sonarqubecloud
Copy link

@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from ba5566e to 773ccd0 Compare June 8, 2025 10:27
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jun 8, 2025

@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from 773ccd0 to 5055c18 Compare July 19, 2025 16:10
@sonarqubecloud
Copy link

@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from 5055c18 to e25395b Compare September 1, 2025 02:19
@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from e25395b to 2bde0ed Compare September 27, 2025 07:14
@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from 2bde0ed to 9f9a81b Compare October 6, 2025 08:09
@sonarqubecloud
Copy link

sonarqubecloud bot commented Oct 6, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant