Skip to content
This repository was archived by the owner on Oct 19, 2022. It is now read-only.

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 2, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
core-js 3.25.3 -> 3.25.5 age adoption passing confidence

Release Notes

zloirock/core-js

v3.25.5

Compare Source

  • Fixed regression with an error on reuse of some built-in methods from another realm, #​1133

v3.25.4

Compare Source

  • Added a workaround of a Nashorn bug with Function.prototype.{ call, apply, bind } on string methods, #​1128
  • Updated lists of [Serializable] and [Transferable] objects in the structuredClone polyfill. Mainly, for better error messages if polyfilling of cloning such types is impossible
  • Array.prototype.{ group, groupToMap } marked as supported from V8 ~ Chromium 108
  • Added Electron 22 compat data mapping

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.

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


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Oct 2, 2022

⚠ 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: frontend/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @vue/cli-plugin-babel@4.5.13
npm ERR! Found: @vue/cli-service@5.0.1
npm ERR! node_modules/@vue/cli-service
npm ERR!   dev @vue/cli-service@"5.0.1" from the root project
npm ERR!   peer @vue/cli-service@"^3.0.0 || ^4.0.0 || ^5.0.0-0" from @vue/cli-plugin-router@5.0.8
npm ERR!   node_modules/@vue/cli-service/node_modules/@vue/cli-plugin-router
npm ERR!     @vue/cli-plugin-router@"^5.0.1" from @vue/cli-service@5.0.1
npm ERR!   1 more (@vue/cli-plugin-vuex)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @vue/cli-service@"^3.0.0 || ^4.0.0-0" from @vue/cli-plugin-babel@4.5.13
npm ERR! node_modules/@vue/cli-plugin-babel
npm ERR!   dev @vue/cli-plugin-babel@"4.5.13" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @vue/cli-service@4.5.19
npm ERR! node_modules/@vue/cli-service
npm ERR!   peer @vue/cli-service@"^3.0.0 || ^4.0.0-0" from @vue/cli-plugin-babel@4.5.13
npm ERR!   node_modules/@vue/cli-plugin-babel
npm ERR!     dev @vue/cli-plugin-babel@"4.5.13" 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/2022-10-03T21_19_41_497Z-debug-0.log

@renovate renovate bot force-pushed the renovate/core-js-3.x branch from d0ef850 to 6df719e Compare October 3, 2022 21:19
@renovate renovate bot changed the title Update dependency core-js to v3.25.4 Update dependency core-js to v3.25.5 Oct 3, 2022
@ju-c ju-c closed this Oct 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants