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 jest monorepo #928

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 22, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/jest (source) 29.5.3 -> 29.5.14 age adoption passing confidence
jest (source) 29.6.4 -> 29.7.0 age adoption passing confidence
jest-cli (source) 29.6.4 -> 29.7.0 age adoption passing confidence

Release Notes

jestjs/jest (jest)

v29.7.0

Compare Source

Features
  • [create-jest] Add npm init / yarn create initialiser for Jest projects (#​14465)
  • [jest-validate] Allow deprecation warnings for unknown options (#​14499)
Fixes
  • [jest-resolver] Replace unmatched capture groups in moduleNameMapper with empty string instead of undefined (#​14507)
  • [jest-snapshot] Allow for strings as well as template literals in inline snapshots (#​14465)
  • [@jest/test-sequencer] Calculate test runtime if perStats.duration is missing (#​14473)
Performance
  • [@jest/create-cache-key-function] Cache access of NODE_ENV and BABEL_ENV (#​14455)
Chore & Maintenance
  • [jest-cli] Move internal config initialisation logic to the create-jest package (#​14465)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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
Contributor Author

renovate bot commented Aug 22, 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: direflow/package-lock.json
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/react
npm ERR!   react@"18.2.0" from the root project
npm ERR!   peer react@"^18.2.0" from [email protected]
npm ERR!   node_modules/react-dom
npm ERR!     react-dom@"18.2.0" from the root project
npm ERR!   3 more (react-scripts, react-shallow-renderer, react-test-renderer)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"16.13.1" from [email protected]
npm ERR! node_modules/direflow-component
npm ERR!   direflow-component@"3.5.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"16.13.1" from [email protected]
npm ERR!   node_modules/direflow-component
npm ERR!     direflow-component@"3.5.5" 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/renovate/cache/others/npm/_logs/2024-02-01T17_32_26_253Z-eresolve-report.txt

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

@renovate renovate bot force-pushed the renovate/jest-monorepo branch 3 times, most recently from 3daa57d to 6d3867a Compare August 28, 2023 15:21
@renovate renovate bot changed the title chore(deps): update dependency @types/jest to v29.5.4 chore(deps): update jest monorepo Sep 12, 2023
@renovate renovate bot force-pushed the renovate/jest-monorepo branch 2 times, most recently from aacbfe1 to f7ffeed Compare September 15, 2023 22:17
@renovate renovate bot force-pushed the renovate/jest-monorepo branch from f7ffeed to c1d74c5 Compare October 18, 2023 07:06
@renovate renovate bot force-pushed the renovate/jest-monorepo branch from c1d74c5 to d4e2841 Compare October 30, 2023 21:33
@renovate renovate bot force-pushed the renovate/jest-monorepo branch from d4e2841 to a29a69c Compare November 7, 2023 23:22
@renovate renovate bot force-pushed the renovate/jest-monorepo branch 2 times, most recently from 1aefad9 to c891753 Compare November 22, 2023 02:14
@renovate renovate bot force-pushed the renovate/jest-monorepo branch from c891753 to 913004a Compare December 6, 2023 01:27
@renovate renovate bot force-pushed the renovate/jest-monorepo branch from 913004a to 9b0d914 Compare February 1, 2024 17:32
@renovate renovate bot changed the title chore(deps): update jest monorepo chore(deps): update jest monorepo to v29.7.0 Jul 12, 2024
@renovate renovate bot changed the title chore(deps): update jest monorepo to v29.7.0 chore(deps): update jest monorepo Jul 12, 2024
@renovate renovate bot force-pushed the renovate/jest-monorepo branch from 9b0d914 to 1d5254f Compare September 12, 2024 18:33
Copy link
Contributor Author

renovate bot commented Sep 12, 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: direflow/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @natds/[email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"18.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"17.0.2" from [email protected]
npm error node_modules/direflow-component
npm error   direflow-component@"4.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 /tmp/renovate/cache/others/npm/_logs/2024-12-09T12_00_30_187Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-09T12_00_30_187Z-debug-0.log

@renovate renovate bot force-pushed the renovate/jest-monorepo branch from 1d5254f to 69325d3 Compare October 11, 2024 17:13
@renovate renovate bot force-pushed the renovate/jest-monorepo branch from 69325d3 to f9fce1c Compare October 23, 2024 03:57
@renovate renovate bot changed the title chore(deps): update jest monorepo chore(deps): update dependency jest to v29.7.0 Dec 8, 2024
@renovate renovate bot changed the title chore(deps): update dependency jest to v29.7.0 chore(deps): update jest monorepo Dec 8, 2024
@renovate renovate bot force-pushed the renovate/jest-monorepo branch 2 times, most recently from b3d487a to c1e8923 Compare December 9, 2024 07:56
@renovate renovate bot force-pushed the renovate/jest-monorepo branch from c1e8923 to fc8c453 Compare December 9, 2024 12:00
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