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

[dependabot]

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

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 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)

[dependabot]

Looks like @metamask/create-release-branch is up-to-date now, so this is no longer needed.