chore: Update `ts-jest`

[Gudahtt]

Explanation

Update ts-jest to resolve peer dependency warning about the version of typescript we're using being too high.

The changelogs for the two breaking changes of ts-jest are here:

• 28: https://github.com/kulshekhar/ts-jest/blob/main/CHANGELOG.md#2800-2022-05-02
• 29: https://github.com/kulshekhar/ts-jest/blob/main/CHANGELOG.md#2900-2022-09-08

None of the breaking changes seem to impact us.

References

N/A

Checklist

• [x] I've updated the test suite for new or updated code as appropriate
• [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• [x] I've communicated my changes to consumers by updating changelogs for packages I've changed, highlighting breaking changes as necessary
• [x] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

[socket-security[bot]]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	jest-environment-jsdom@​27.5.1 ⏵ 28.1.3			+1
	jest-environment-node@​27.5.1 ⏵ 29.7.0	+1		+1
	jest@​27.5.1 ⏵ 28.1.3			+1
	@​types/​jest@​27.5.2 ⏵ 28.1.8	+1		+1
	ts-jest@​27.1.5 ⏵ 28.0.8

View full report

[socket-security[bot]]

[!WARNING] MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Potential code anomaly (AI signal): npm http-proxy-agent is 100.0% likely to have a medium risk anomaly Notes: The code fragment is a conventional HTTP proxy agent component handling optional proxy authentication and dynamic header adjustments. There is no evidence of malicious activity, data exfiltration, or supply-chain abuse within this fragment. The main concerns relate to reliance on internal Node.js fields (version fragility) and potential in-memory exposure of credentials, but these are standard operational caveats for proxy clients and do not indicate malice. Confidence: 1.00 Severity: 0.60 From: ? → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Ignoring alerts on:

• [email protected]

View full report

[Gudahtt]

@SocketSecurity ignore npm/[email protected]

"new author" from 3 years ago is not a concern. Also this is a well known maintainer