Skip to content

chore(deps): update dependency jasmine-core to ~4.6.0 - #7

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/jasmine-monorepo
Open

chore(deps): update dependency jasmine-core to ~4.6.0#7
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/jasmine-monorepo

Conversation

@renovate

@renovaterenovateBot commented Mar 16, 2023

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

PackageChangeAgeConfidence
jasmine-core (source)~4.5.0~4.6.0ageconfidence

Release Notes

jasmine/jasmine (jasmine-core)

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: (UTC)

  • 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.

🔕 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

renovateBot commented Mar 16, 2023

Copy link
Copy Markdown
ContributorAuthor

⚠ 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 unable to resolve dependency tree
npm ERR! npm ERR! While resolving: angular-standalone@0.0.0
npm ERR! Found: @angular/compiler-cli@15.2.9
npm ERR! node_modules/@angular/compiler-cli
npm ERR! dev @angular/compiler-cli@"^15.1.0" from the root project
npm ERR! npm ERR! Could not resolve dependency:
npm ERR! peer @angular/compiler-cli@"^16.1.0" from @angular-devkit/build-angular@16.1.0
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR! dev @angular-devkit/build-angular@"^16.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/69130e/35f4aa/cache/others/npm/_logs/2023-06-15T21_58_26_792Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /tmp/worker/69130e/35f4aa/cache/others/npm/_logs/2023-06-15T21_58_26_792Z-debug-0.log

@renovate
renovateBotforce-pushed the renovate/jasmine-monorepo branch 2 times, most recently from 02c2af2 to 710bb1bCompareJune 15, 2023 21:59
@renovate
renovateBotforce-pushed the renovate/jasmine-monorepo branch from 710bb1b to 5e37dfbCompareAugust 10, 2025 14:55
@renovate

renovateBot commented Aug 10, 2025

Copy link
Copy Markdown
ContributorAuthor

⚠️ 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. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: angular-standalone@0.0.0
npm error Found: zone.js@0.12.0
npm error node_modules/zone.js
npm error zone.js@"~0.12.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer zone.js@"~0.13.0" from @angular/core@16.2.12
npm error node_modules/@angular/core
npm error @angular/core@"^16.0.0" from the root project
npm error peer @angular/core@"16.2.12" from @angular/animations@16.2.12
npm error node_modules/@angular/animations
npm error @angular/animations@"^16.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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/2026-08-14T20_41_08_054Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-14T20_41_08_054Z-debug-0.log

@renovaterenovateBot changed the title chore(deps): update dependency jasmine-core to ~4.6.0chore(deps): update jasmine monorepo to ~4.6.0Jun 2, 2026
@renovaterenovateBot changed the title chore(deps): update jasmine monorepo to ~4.6.0chore(deps): update jasmine monorepoJun 22, 2026
@renovaterenovateBot changed the title chore(deps): update jasmine monorepochore(deps): update dependency jasmine-core to ~4.6.0Jun 25, 2026
Sign up for freeto 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