Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 23, 2024

Bumps @metamask/create-release-branch from 2.0.1 to 3.0.0.

Release notes

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

3.0.0

Changed

  • BREAKING: Format changelogs using Prettier (#100)
    • This is a breaking change since it changes the default formatting of the changelog in new release PRs. If you have a package script that runs auto-changelog validate, or you're calling auto-changelog validate in CI, you'll now need to pass the --prettier flag (see example).

Fixed

  • Restore support for monorepos that use workspace:^ references for interdependencies (#125)
Changelog

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

[3.0.0]

Changed

  • BREAKING: Format changelogs using Prettier (#100)
    • This is a breaking change since it changes the default formatting of the changelog in new release PRs. If you have a package script that runs auto-changelog validate, or you're calling auto-changelog validate in CI, you'll now need to pass the --prettier flag (see example).

Fixed

  • Restore support for monorepos that use workspace:^ references for interdependencies (#125)
Commits

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 will merge this PR once CI passes on it, as requested by @mcmire.


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)

Bumps [@metamask/create-release-branch](https://github.com/MetaMask/create-release-branch) from 2.0.1 to 3.0.0.
- [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@v2.0.1...v3.0.0)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot requested a review from a team as a code owner January 23, 2024 13:00
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 23, 2024
@socket-security
Copy link

socket-security bot commented Jan 23, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@metamask/create-release-branch@3.0.0 Transitive: environment, filesystem, network, shell, unsafe +72 18.1 MB metamaskbot
npm/get-stream@8.0.1 None 0 25.2 kB ehmicky
npm/human-signals@5.0.0 None 0 26 kB ehmicky

🚮 Removed packages: npm/@metamask/create-release-branch@2.0.1

View full report↗︎

@socket-security
Copy link

socket-security bot commented Jan 23, 2024

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package Note
New author npm/get-stream@8.0.1

View full report↗︎

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

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.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/get-stream@8.0.1

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 23, 2024

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

2 similar comments
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 23, 2024

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 23, 2024

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

@mcmire
Copy link
Contributor

mcmire commented Jan 23, 2024

@dependabot squash and merge

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 23, 2024

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 23, 2024

Dependabot tried to merge this PR, but received the following error from GitHub:

Waiting on code owner review from MetaMask/devs.

@mcmire
Copy link
Contributor

mcmire commented Jan 23, 2024

@dependabot squash and merge

@dependabot dependabot bot merged commit f4b889a into main Jan 23, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/metamask/create-release-branch-3.0.0 branch January 23, 2024 17:51
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants