Skip to content

chore(deps-dev): bump @metamask/create-release-branch from 4.1.3 to 4.2.2 - #461

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/main/metamask/create-release-branch-4.2.2
Open

chore(deps-dev): bump @metamask/create-release-branch from 4.1.3 to 4.2.2#461
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/main/metamask/create-release-branch-4.2.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 31, 2026

Copy link
Copy Markdown
Contributor

Bumps @metamask/create-release-branch from 4.1.3 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)

4.2.1

Changed

  • Bump @metamask/auto-changelog from 6.1.0 to 6.1.1 (#200)

4.2.0

Added

  • Add option to use Oxfmt for formatting changelog (#198)
    • The CLI now accepts an optional --formatter option which can be set to either "oxfmt" or "prettier" (default).

4.1.4

Changed

  • When a new major version of a package is being released but some of its direct dependents are missing, strongly suggest that they be included in the release as well (#193)
  • Update UI to improve how existing per-package error messages are shown so they are less prominent visually and provide clearer rationales/examples (#192)
Changelog

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

[4.2.2]

Fixed

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

[4.2.1]

Changed

  • Bump @metamask/auto-changelog from 6.1.0 to 6.1.1 (#200)

[4.2.0]

Added

  • Add option to use Oxfmt for formatting changelog (#198)
    • The CLI now accepts an optional --formatter option which can be set to either "oxfmt" or "prettier" (default).

[4.1.4]

Changed

  • When a new major version of a package is being released but some of its direct dependents are missing, strongly suggest that they be included in the release as well (#193)
  • Update UI to improve how existing per-package error messages are shown so they are less prominent visually and provide clearer rationales/examples (#192)
Commits
Maintainer changes

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


Dependabot compatibility score

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)

Bumps [@metamask/create-release-branch](https://github.com/MetaMask/create-release-branch) from 4.1.3 to 4.2.2.
- [Release notes](https://github.com/MetaMask/create-release-branch/releases)
- [Changelog](https://github.com/MetaMask/create-release-branch/blob/main/CHANGELOG.md)
- [Commits](MetaMask/create-release-branch@v4.1.3...v4.2.2)

---
updated-dependencies:
- dependency-name: "@metamask/create-release-branch"
  dependency-version: 4.2.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 31, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner August 31, 2026 06:03
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 31, 2026
@socket-security

Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​metamask/​create-release-branch@​4.1.3 ⏵ 4.2.280 -1100100 +692 +4100

View full report

@socket-security

Copy link
Copy Markdown

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 Medium
Network access: npm @octokit/request in module globalThis["fetch"]

Module: globalThis["fetch"]

Location: Package overview

From: package.jsonnpm/@metamask/create-release-branch@4.2.2npm/@octokit/request@8.4.1

ℹ Read more on: This package | This alert | What is network access?

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: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@octokit/request@8.4.1. 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.

Warn Low
Environment variable access: npm @metamask/auto-changelog

Location: Package overview

From: package.jsonnpm/@metamask/create-release-branch@4.2.2npm/@metamask/auto-changelog@6.2.1

ℹ Read more on: This package | This alert | What is environment variable access?

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: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/auto-changelog@6.2.1. 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.

Warn Low
Environment variable access: npm @metamask/auto-changelog reads npm_package_repository_url

Env Vars: npm_package_repository_url

Location: Package overview

From: package.jsonnpm/@metamask/create-release-branch@4.2.2npm/@metamask/auto-changelog@6.2.1

ℹ Read more on: This package | This alert | What is environment variable access?

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: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/auto-changelog@6.2.1. 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.

Warn Low
Environment variable access: npm @metamask/auto-changelog reads PROJECT_CWD

Env Vars: PROJECT_CWD

Location: Package overview

From: package.jsonnpm/@metamask/create-release-branch@4.2.2npm/@metamask/auto-changelog@6.2.1

ℹ Read more on: This package | This alert | What is environment variable access?

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: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/auto-changelog@6.2.1. 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.

Warn Low
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.jsonnpm/@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants