Skip to content

Update jest monorepo to v30.3.0#894

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/jest-monorepo
Closed

Update jest monorepo to v30.3.0#894
renovate[bot] wants to merge 1 commit intomainfrom
renovate/jest-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 11, 2026

This PR contains the following updates:

Package Change Age Confidence
@jest/globals (source) 30.2.030.3.0 age confidence
jest (source) 30.2.030.3.0 age confidence

Release Notes

jestjs/jest (@​jest/globals)

v30.3.0

Compare Source

Features
  • [jest-config] Add defineConfig and mergeConfig helpers for type-safe Jest config (#​15844)
  • [jest-fake-timers] Add setTimerTickMode to configure how timers advance
  • [*] Reduce token usage when run through LLMs (3f17932)
Fixes
  • [jest-config] Keep CLI coverage output when using --json with --outputFile (#​15918)
  • [jest-mock] Use Symbol from test environment (#​15858)
  • [jest-reporters] Fix issue where console output not displayed for GHA reporter even with silent: false option (#​15864)
  • [jest-runtime] Fix issue where user cannot utilize dynamic import despite specifying --experimental-vm-modules Node option (#​15842)
  • [jest-test-sequencer] Fix issue where failed tests due to compilation errors not getting re-executed even with --onlyFailures CLI option (#​15851)
  • [jest-util] Make sure process.features.require_module is false (#​15867)
Chore & Maintenance
  • [*] Replace remaining micromatch uses with picomatch
  • [deps] Update to sinon/fake-timers v15
  • [docs] Update V30 migration guide to notify users on jest.mock() work with case-sensitive path (#​15849)
  • Updated Twitter icon to match the latest brand guidelines (#​15869)

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.

@renovate
Copy link
Contributor Author

renovate bot commented Mar 11, 2026

⚠️ 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.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @eslint/[email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"^9.39.2" from the root project
npm error   peer eslint@"^7.5.0 || ^8.0.0 || ^9.0.0" from @babel/[email protected]
npm error   node_modules/@babel/eslint-parser
npm error     dev @babel/eslint-parser@"^7.28.6" from the root project
npm error   7 more (@eslint-community/eslint-utils, @eslint/compat, ...)
npm error
npm error Could not resolve dependency:
npm error peerOptional eslint@"^10.0.0" from @eslint/[email protected]
npm error node_modules/@eslint/js
npm error   dev @eslint/js@"^10.0.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peerOptional eslint@"^10.0.0" from @eslint/[email protected]
npm error   node_modules/@eslint/js
npm error     dev @eslint/js@"^10.0.1" 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 /runner/cache/others/npm/_logs/2026-03-11T00_35_54_960Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-11T00_35_54_960Z-debug-0.log

@sir-gon sir-gon force-pushed the renovate/jest-monorepo branch from 02707e8 to a029fb2 Compare March 11, 2026 00:35
@sir-gon sir-gon closed this Mar 11, 2026
@sir-gon sir-gon deleted the renovate/jest-monorepo branch March 11, 2026 00:58
@renovate
Copy link
Contributor Author

renovate bot commented Mar 11, 2026

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (^30.0.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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.

1 participant