Skip to content

chore(deps): update jest monorepo to v30 (major) #32

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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 14, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/jest (source) ^29.5.12 -> ^30.0.0 age adoption passing confidence
jest (source) ^29.7.0 -> ^30.0.0 age adoption passing confidence

Release Notes

jestjs/jest (jest)

v30.0.2

Compare Source

v30.0.1

Compare Source

v30.0.0

Compare Source


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 these updates 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 Jun 14, 2025

⚠️ 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: npm-shrinkwrap.json
npm warn cli npm v11.4.2 does not support Node.js v18.19.0. This version of npm supports the following node versions: `^20.17.0 || >=22.9.0`. You can find the latest version at https://nodejs.org/.
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm warn Unknown project config "strict-peer-dependencies". This will stop working in the next major version of npm.
npm warn Unknown project config "auto-install-peers". This will stop working in the next major version of npm.
npm warn Unknown project config "store-dir". This will stop working in the next major version of npm.
npm warn Unknown project config "virtual-store-dir". This will stop working in the next major version of npm.
npm error Cannot read properties of null (reading 'matches')
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-06-21T23_57_51_990Z-debug-0.log

@renovate renovate bot requested a review from mdirshaddev as a code owner June 14, 2025 07:58
Copy link

changeset-bot bot commented Jun 14, 2025

⚠️ No Changeset found

Latest commit: dada284

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/major-jest-monorepo branch from 4b5eca6 to dada284 Compare June 21, 2025 23:58
@renovate renovate bot changed the title chore(deps): update dependency jest to v30 chore(deps): update jest monorepo to v30 (major) Jun 21, 2025
Sign up for free to 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