build(deps-dev): bump @metamask/create-release-branch from 3.1.0 to 4.1.3 #292

dependabot · 2025-05-27T12:50:30Z

Bumps @metamask/create-release-branch from 3.1.0 to 4.1.3.

Release notes

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

4.1.3

Fixed

When creating a new release and populating the Unreleased section, use the same repo URLs in PR links as auto-changelog update would use (#165)

This prevents the updated changelog that create-release-branch produces from being invalid in the case where a non-standard URL was used to clone the repo originally.

4.1.2

Fixed

Improved error handling when opening browser fails due to System Events permissions or non-standard browser configurations (#178)

Now provides clear manual URL instructions instead of failing with osascript errors

Handles both cases: when terminal lacks System Events permissions and when using alternative browsers like Brave

4.1.1

Fixed

Ask users to include peer dependents of a major-bumped package in the release, even they've had no changes (#173)

UI: Include all peer dependents of a major-bumped package as available packages to release, even if they've had no changes (#173)

4.1.0

Added

Add interactive web UI for selecting package versions to release (#166)

Added --interactive (-i) flag to launch a web-based UI for easier version selection

Added --port option to configure the web server port (default: 3000)

Changed

Refine breaking change dependent detection to only consider peer dependencies (#170)

This change supports our policy of requiring packages with breaking changes to be released alongside their dependents

Regular dependencies are no longer included in this check

Allow npm:name@version dependency redirections in manifest (#158)

4.0.0

Changed

BREAKING: Bump minimum Node.js version to ^18.18 (#156)

BREAKING: Bump @metamask/auto-changelog to ^4.0.0 (#156)

This requires prettier@>=3.0.0.

Changelog

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

[4.1.3]

Fixed

When creating a new release and populating the Unreleased section, use the same repo URLs in PR links as auto-changelog update would use (#165)

This prevents the updated changelog that create-release-branch produces from being invalid in the case where a non-standard URL was used to clone the repo originally.

[4.1.2]

Fixed

Improved error handling when opening browser fails due to System Events permissions or non-standard browser configurations (#178)

Now provides clear manual URL instructions instead of failing with osascript errors

Handles both cases: when terminal lacks System Events permissions and when using alternative browsers like Brave

[4.1.1]

Fixed

Ask users to include peer dependents of a major-bumped package in the release, even they've had no changes (#173)

UI: Include all peer dependents of a major-bumped package as available packages to release, even if they've had no changes (#173)

[4.1.0]

Added

Add interactive web UI for selecting package versions to release (#166)

Added --interactive (-i) flag to launch a web-based UI for easier version selection

Added --port option to configure the web server port (default: 3000)

Changed

Refine breaking change dependent detection to only consider peer dependencies (#170)

This change supports our policy of requiring packages with breaking changes to be released alongside their dependents

Regular dependencies are no longer included in this check

Allow npm:name@version dependency redirections in manifest (#158)

[4.0.0]

Changed

BREAKING: Bump minimum Node.js version to ^18.18 (#156)

BREAKING: Bump @metamask/auto-changelog to ^4.0.0 (#156)

This requires prettier@>=3.0.0.

Commits

7ba6cd2 4.1.3 (#182)
814254b Fix repo links in updated changelogs to match auto-changelog (#165)
8e22513 4.1.2 (#180)
748288e docs: format CHANGELOG.md with prettier (#181)
4379de7 chore: bump action-create-release-pr to v3 (#179)
ab18dc4 chore: update security-code-scanner@main to action-security-code-scanner@v1 (...
6960373 fix: gracefully handle browser open failures (#178)
e4630b3 4.1.1 (#174)
fd93e9c fix: include unchanged dependents in release validation (#173)
c2ef169 4.1.0 (#172)
Additional commits viewable in compare view

You can trigger a rebase of this PR 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 merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

socket-security · 2025-05-27T12:51:06Z

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

Diff	Package	Supply Chain Security	Quality
	array-flatten@1.1.1
	side-channel@1.1.0
	bundle-name@4.1.0
	default-browser-id@5.0.0
	is-wsl@3.1.0
	utils-merge@1.0.1
	is-docker@3.0.0
	default-browser@5.2.1
	setprototypeof@1.2.0
	is-inside-container@1.0.0
	cookie-signature@1.0.6
	path-to-regexp@0.1.12
	escape-html@1.0.3
	define-lazy-prop@3.0.0
	@metamask/create-release-branch@3.1.0 ⏵ 4.1.3	⁺¹	⁺¹
	merge-descriptors@1.0.3
	depd@2.0.0
	run-applescript@7.0.0
	ipaddr.js@1.9.1
	side-channel-list@1.0.0
	side-channel-map@1.0.1
	destroy@1.2.0
	ee-first@1.1.1
	on-finished@2.4.1
	side-channel-weakmap@1.0.2
	bytes@3.1.2
	proxy-addr@2.0.7
	forwarded@0.2.0
	encodeurl@2.0.0
	raw-body@2.5.2
See 24 more rows in the dashboard

View full report

socket-security · 2025-05-27T12:51:08Z

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Block		`@metamask/[email protected]` has Network access. Module: globalThis["fetch"] Location: Package overview From: package.json → `npm/@metamask/[email protected]` ℹ 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 `[email protected]`. 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/@metamask/[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.
Block		`[email protected]` has Network access. Module: http-errors Location: Package overview From: yarn.lock → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		`[email protected]` has Network access. Module: net Location: Package overview From: yarn.lock → `npm/[email protected]` → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		`[email protected]` has Network access. Module: http Location: Package overview From: yarn.lock → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		`[email protected]` has Network access. Module: http Location: Package overview From: yarn.lock → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		`[email protected]` has Network access. Module: http-errors Location: Package overview From: yarn.lock → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		`[email protected]` has Network access. Module: http-errors Location: Package overview From: yarn.lock → `npm/[email protected]` ℹ 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 `[email protected]`. 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/[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.
Block		`[email protected]` has a New author. New Author: ulisesgascon Previous Author: dougwilson From: yarn.lock → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is new author? 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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. 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.
Block		`[email protected]` has a New author. New Author: blakeembrey Previous Author: dougwilson From: yarn.lock → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is new author? 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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. 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.
Block		`[email protected]` has a New author. New Author: jonchurch Previous Author: ulisesgascon From: yarn.lock → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is new author? 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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. 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.
Block		`[email protected]` has a New author. New Author: ulisesgascon Previous Author: wesleytodd From: yarn.lock → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is new author? 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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. 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.

View full report

Bumps [@metamask/create-release-branch](https://github.com/MetaMask/create-release-branch) from 3.1.0 to 4.1.3. - [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@v3.1.0...v4.1.3) --- updated-dependencies: - dependency-name: "@metamask/create-release-branch" dependency-version: 4.1.3 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels May 27, 2025

dependabot bot requested review from a team as code owners May 27, 2025 12:50

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels May 27, 2025

gantunesr assigned ccharly and unassigned ccharly Jun 11, 2025

dependabot bot force-pushed the dependabot/npm_and_yarn/metamask/create-release-branch-4.1.3 branch 2 times, most recently from 965e417 to 968a27b Compare June 18, 2025 14:28

dependabot bot force-pushed the dependabot/npm_and_yarn/metamask/create-release-branch-4.1.3 branch from 968a27b to 8015d79 Compare June 18, 2025 14:43

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

build(deps-dev): bump @metamask/create-release-branch from 3.1.0 to 4.1.3 #292

build(deps-dev): bump @metamask/create-release-branch from 3.1.0 to 4.1.3 #292

Uh oh!

dependabot bot commented on behalf of github May 27, 2025 •

edited

Loading

Uh oh!

socket-security bot commented May 27, 2025 •

edited

Loading

Uh oh!

socket-security bot commented May 27, 2025 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

build(deps-dev): bump @metamask/create-release-branch from 3.1.0 to 4.1.3 #292

Are you sure you want to change the base?

build(deps-dev): bump @metamask/create-release-branch from 3.1.0 to 4.1.3 #292

Uh oh!

Conversation

dependabot bot commented on behalf of github May 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

4.1.3

Fixed

4.1.2

Fixed

4.1.1

Fixed

4.1.0

Added

Changed

4.0.0

Changed

[4.1.3]

Fixed

[4.1.2]

Fixed

[4.1.1]

Fixed

[4.1.0]

Added

Changed

[4.0.0]

Changed

Uh oh!

socket-security bot commented May 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security bot commented May 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

dependabot bot commented on behalf of github May 27, 2025 •

edited

Loading

socket-security bot commented May 27, 2025 •

edited

Loading

socket-security bot commented May 27, 2025 •

edited

Loading