[deps] SM: Update jest-mock-extended to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
jest-mock-extended	3.0.7 -> 4.0.0

---

Release Notes

marchaos/jest-mock-extended (jest-mock-extended)

v4.0.0

Compare Source

Upgrade to jest 30

---

Configuration

📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (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.

[bitwarden-bot]

Internal tracking:

• ID: SM-1506
• Link: https://bitwarden.atlassian.net/browse/SM-1506

[cd-bitwarden]

Tested everything locally, this looks good

[claude]

Claude finished @renovate[bot]'s task —— View job

---

Review Complete

Summary

This PR attempts to upgrade jest-mock-extended from v3.0.7 to v4.0.0. However, this upgrade is incompatible with the project's current Jest configuration.

---

Findings

Finding 1: Incompatible Jest version (❌ Major - blocking)

Issue: jest-mock-extended v4.0.0 requires Jest 30, but this project currently uses Jest 29.

Evidence:

• Current jest-preset-angular: 14.6.1 (requires Jest ^29.0.0)
• jest-mock-extended v4.0.0 peer dependencies require Jest ^30.0.0
• This exact upgrade was previously attempted and reverted in commit b3b6df8859 with the message: "The update to jest-mock-extended v4.0.0 was incompatible with the project's current Jest 29 installation"

Impact: This PR will cause the same compatibility issues that led to the previous revert, including npm installation failures and test failures.

Resolution Required: This PR should not be merged until Jest is upgraded to v30. I can see there's work in progress on a "SM-Jest" branch that upgrades jest-preset-angular to v15.0.3 (which supports Jest 30). This jest-mock-extended upgrade should wait for that Jest 30 upgrade to be completed and merged first.

---

Finding 2: PR lacks proper context (💭 Inquiry)

The PR description doesn't mention:

• The Jest version compatibility requirement
• The previous revert (commit b3b6df8859)
• The dependency on the Jest 30 upgrade effort

Recommendation: Update the PR description to note that this depends on the Jest 30 upgrade being completed first, or close this PR until Jest 30 is available in main.

---

Recommendation

Do not merge this PR until:

1. Jest is upgraded to v30 in the main branch
2. The SM-Jest branch (or equivalent) with jest-preset-angular v15+ is merged
3. This PR is rebased on top of the Jest 30 upgrade

The human reviewer (@cd-bitwarden) approved this after testing locally, which suggests the compatibility issue may not be immediately obvious in local testing. However, the previous CI failures and revert demonstrate this will cause issues in production.

[github-actions]

Checkmarx One – Scan Summary & Details – 35aa7c1b-f2f4-4ee1-96a4-185ae1dbd51a

Great job! No new security vulnerabilities introduced in this pull request

[claude]

This upgrade to v4.0.0 requires Jest 30, but the project currently uses Jest 29 (via jest-preset-angular 14.6.1).

This exact change was previously reverted in commit b3b6df8859 due to compatibility issues. The upgrade should wait until the Jest 30 migration (SM-Jest branch with jest-preset-angular v15+) is merged to main.

[cd-bitwarden]

Placing on hold until we can upgrade to Jest 30, it is required for this PR.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

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