chore: Bump @metamask/create-release-branch from 4.2.1 to 4.2.2

[dependabot]

Bumps @metamask/create-release-branch from 4.2.1 to 4.2.2.

Release notes

Sourced from @​metamask/create-release-branch's releases.

4.2.2

Fixed

• Bump @metamask/action-utils to ^2.0.0 (#206)

Changelog

Sourced from @​metamask/create-release-branch's changelog.

[4.2.2]

Fixed

• Bump @metamask/action-utils to ^2.0.0 (#206)

Commits

• 29b1810 4.2.2 (#207)
• 7c0b750 fix: Bump action-utils to ^2.0.0 (#206)
• c80c69b ci: Upgrade Yarn to 4.16.0 and align workflows with module template (#204)
• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​metamask/create-release-branch since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​metamask/​create-release-branch@​4.2.1 ⏵ 4.2.2	-1			+4

View full report

[socket-security]

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 @metamask/create-release-branch is 66.0% likely to have a medium risk anomaly Notes: No clear indicators of covert malware (tracking/exfiltration/backdoor) are present in this module’s logic. However, it exposes a high-impact release execution capability over HTTP without authentication/authorization, and it can read changelog files from disk and return them over the network. If an attacker can reach the server port, they could potentially trigger unintended release actions and repository commits (impact depends on how strictly downstream helpers validate and constrain operations). Confidence: 0.66 Severity: 0.62 From: package.json → npm/@metamask/create-release-branch@4.2.2 ℹ 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 support@socket.dev. 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/@metamask/create-release-branch@4.2.2. 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.

View full report