Skip to content

Bump @metamask/create-release-branch from 1.1.0 to 2.0.1#2022

Merged
FrederikBolding merged 2 commits intomainfrom
dependabot/npm_and_yarn/main/metamask/create-release-branch-2.0.1
Dec 13, 2023
Merged

Bump @metamask/create-release-branch from 1.1.0 to 2.0.1#2022
FrederikBolding merged 2 commits intomainfrom
dependabot/npm_and_yarn/main/metamask/create-release-branch-2.0.1

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Dec 8, 2023

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.


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

Release notes

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

2.0.1

Fixed

  • Move @metamask/auto-changelog from devDependencies to dependencies and pin to ~3.3.0 (#122)

2.0.0

Changed

  • BREAKING Bump minimum Node version to 16 (#114)
  • Reorder workflow to update changelogs first (#109)
    • When you run this tool you can use the changelogs to decide which versions to include in your release.
  • Allow for partial releases (#98)
    • It is no longer necessary to release every package that has changed. Instead, you may release a subset of packages (as long as it is okay to do so; see next items).
  • Soft-enforce major-bumped packages to be released along with their dependents (#101)
    • If a new major version of a package A is being included in the release, and there are is a package B which depends on A but which is not also being released at the same time, then the tool will produce an error. This is to ensure that if a consumer is upgrading package A in a project and they also need to upgrade package B for compatibility reasons, they can.
  • Soft-enforce dependents to be released along with their dependencies (#102)
    • If package B depends on package A, and A has changed since its last release, and B is being included in the release but not A, then the tool will produce an error. This is to ensure that if B has been changed to rely on a new feature that was added to A, it doesn't break when it is used in a project (since that feature is present in development but has not been published).
Changelog

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

[2.0.1]

Fixed

  • Move @metamask/auto-changelog from devDependencies to dependencies and pin to ~3.3.0 (#122)

[2.0.0]

Changed

  • BREAKING Bump minimum Node version to 16 (#114)
  • Reorder workflow to update changelogs first (#109)
    • When you run this tool you can use the changelogs to decide which versions to include in your release.
  • Allow for partial releases (#98)
    • It is no longer necessary to release every package that has changed. Instead, you may release a subset of packages (as long as it is okay to do so; see next items).
  • Soft-enforce major-bumped packages to be released along with their dependents (#101)
    • If a new major version of a package A is being included in the release, and there are is a package B which depends on A but which is not also being released at the same time, then the tool will produce an error. This is to ensure that if a consumer is upgrading package A in a project and they also need to upgrade package B for compatibility reasons, they can.
  • Soft-enforce dependents to be released along with their dependencies (#102)
    • If package B depends on package A, and A has changed since its last release, and B is being included in the release but not A, then the tool will produce an error. This is to ensure that if B has been changed to rely on a new feature that was added to A, it doesn't break when it is used in a project (since that feature is present in development but has not been published).
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 it's up-to-date and CI passes on it, as requested by @FrederikBolding.


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 1.1.0 to 2.0.1.
- [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@v1.1.0...v2.0.1)

---
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 December 8, 2023 06:12
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Dec 8, 2023
@socket-security
Copy link
Copy Markdown

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages Version New capabilities Transitives Size Publisher
@metamask/create-release-branch 1.1.0...2.0.1 None +1/-0 429 kB metamaskbot

@codecov
Copy link
Copy Markdown

codecov bot commented Dec 8, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (cd57539) 96.10% compared to head (e6ae784) 96.10%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2022   +/-   ##
=======================================
  Coverage   96.10%   96.10%           
=======================================
  Files         269      269           
  Lines        6286     6286           
  Branches     1011     1011           
=======================================
  Hits         6041     6041           
  Misses        245      245           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@FrederikBolding
Copy link
Copy Markdown
Member

@dependabot merge

@FrederikBolding FrederikBolding merged commit 9dd48bb into main Dec 13, 2023
@FrederikBolding FrederikBolding deleted the dependabot/npm_and_yarn/main/metamask/create-release-branch-2.0.1 branch December 13, 2023 09:49
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.

1 participant