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 jasmine-core to v5 #299

Open
wants to merge 1 commit into
base: 7.0.x
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 5, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
jasmine-core (source) ~4.6.0 -> ~5.5.0 age adoption passing confidence

Release Notes

jasmine/jasmine (jasmine-core)

v5.5.0

Compare Source

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

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.


Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 6am every weekday" (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.

Copy link
Contributor Author

renovate bot commented Feb 5, 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: webapp/cas-mgmt-webapp-workspace/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: cas-mgmt-webapp-workspace@0.0.0
npm ERR! Found: zone.js@0.14.3
npm ERR! node_modules/zone.js
npm ERR!   zone.js@"~0.14.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.11.4" from @angular/core@13.4.0
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"13.4.0" from the root project
npm ERR!   peer @angular/core@"13.4.0" from @angular/animations@13.4.0
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"~13.4.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-02-05T22_17_47_355Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from 6a8b2fd to 154f492 Compare July 20, 2024 18:34
@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from 154f492 to 6b22c5e Compare September 7, 2024 21:42
@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from 6b22c5e to f099c7e Compare October 12, 2024 19:32
@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from f099c7e to 20c1fb5 Compare October 29, 2024 04:21
@renovate renovate bot force-pushed the renovate/major-jasmine-monorepo branch from 20c1fb5 to 67bdcb5 Compare December 3, 2024 00:01
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.

0 participants