Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 193.0.0 #4643

Merged
merged 11 commits into from
Aug 29, 2024
Merged

Release 193.0.0 #4643

merged 11 commits into from
Aug 29, 2024

Conversation

MajorLift
Copy link
Contributor

@MajorLift MajorLift commented Aug 28, 2024

Explanation

This is a release candidate for v193.0.0.

  • @metamask/approval-controller@7.0.3 (patch)
  • @metamask/base-controller@7.0.0 (major)
  • @metamask/composable-controller@9.0.0 (major)
  • @metamask/keyring-controller@17.2.0 (minor)
  • @metamask/logging-controller@6.0.0 (major)
  • @metamask/message-manager@10.0.3 (patch)
  • @metamask/phishing-controller@12.0.1 (patch)
  • @metamask/signature-controller@19.0.0 (major)

Changelog

### Changed

- Bump `@metamask/approval-controller` from `^7.0.2` to `^7.0.3` ([#4643](https://github.com/MetaMask/core/pull/4643))
- Bump `@metamask/base-controller` from `^6.0.3` to `^7.0.0` ([#4643](https://github.com/MetaMask/core/pull/4643))
- Bump `@metamask/composable-controller` from `^8.0.0` to `^9.0.0` ([#4643](https://github.com/MetaMask/core/pull/4643))
- Bump `@metamask/keyring-controller` from `^17.1.2` to `^17.2.0` ([#4643](https://github.com/MetaMask/core/pull/4643))
- Bump `@metamask/logging-controller` from `^5.0.0` to `^6.0.0` ([#4643](https://github.com/MetaMask/core/pull/4643))
- Bump `@metamask/message-manager` from `^10.0.2` to `^10.0.3` ([#4643](https://github.com/MetaMask/core/pull/4643))
- Bump `@metamask/phishing-controller` from `^12.0.0` to `^12.0.1` ([#4643](https://github.com/MetaMask/core/pull/4643))
- Bump `@metamask/signature-controller` from `^18.1.0` to `^19.0.0` ([#4643](https://github.com/MetaMask/core/pull/4643))

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've highlighted breaking changes using the "BREAKING" category above as appropriate

Copy link

socket-security bot commented Aug 28, 2024

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

🚮 Removed packages: npm/@metamask/logging-controller@5.0.0)

View full report↗︎

@MajorLift
Copy link
Contributor Author

@metamaskbot publish-preview

@MajorLift MajorLift marked this pull request as ready for review August 28, 2024 17:49
@MajorLift MajorLift requested review from a team as code owners August 28, 2024 17:49
Comment on lines +19 to +20
- **BREAKING:** Fix `StateMetadata` type so that it requires associated metadata for all optional and non-optional top-level state properties ([#4612](https://github.com/MetaMask/core/pull/4612))
- Fixes issue of runtime error being thrown during `BaseController` instantiation due to missing metadata for optional state properties.
Copy link
Contributor Author

@MajorLift MajorLift Aug 28, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if we should count this as a breaking change, even though the StateMetadata type has been narrowed.
(∵ T & Required<U> extends T & U extends T & Partial<U> extends T)

@kanthesha @Gudahtt Thoughts? Could we make this a minor release?

Mrtenz
Mrtenz previously approved these changes Aug 28, 2024
jpuri
jpuri previously approved these changes Aug 28, 2024
AugmentedMode
AugmentedMode previously approved these changes Aug 29, 2024
@MajorLift MajorLift dismissed AugmentedMode’s stale review August 29, 2024 13:58

The merge-base changed after approval.

AugmentedMode
AugmentedMode previously approved these changes Aug 29, 2024
@MajorLift MajorLift dismissed AugmentedMode’s stale review August 29, 2024 14:10

The merge-base changed after approval.

imblue-dabadee
imblue-dabadee previously approved these changes Aug 29, 2024
AugmentedMode
AugmentedMode previously approved these changes Aug 29, 2024
Co-authored-by: Jongsun Suh <jongsun.suh@icloud.com>
@AugmentedMode AugmentedMode dismissed stale reviews from imblue-dabadee and themself via ea4443c August 29, 2024 14:45
Copy link
Contributor

@AugmentedMode AugmentedMode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@MajorLift MajorLift merged commit 8eb7cde into main Aug 29, 2024
116 of 117 checks passed
@MajorLift MajorLift deleted the release/193.0.0 branch August 29, 2024 14:54
Comment on lines +12 to +16
### Added

- Add `getHostnameFromUrl` utility function to standardize hostname extraction from URLs ([#4645](https://github.com/MetaMask/core/pull/4645))

### Fixed
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missed this entry. Leaving it here so we can backport it into the changelog in a future commit. @MetaMask/product-safety

Suggested change
### Added
- Add `getHostnameFromUrl` utility function to standardize hostname extraction from URLs ([#4645](https://github.com/MetaMask/core/pull/4645))
### Fixed
### Added
- Add `getHostnameFromUrl` utility function to standardize hostname extraction from URLs ([#4645](https://github.com/MetaMask/core/pull/4645))
### Changed
- Bump `@metamask/base-controller` from `^6.0.3` to `^7.0.0` ([#4643](https://github.com/MetaMask/core/pull/4643))
### Fixed

Prithpal-Sooriya added a commit that referenced this pull request Sep 5, 2024
## Explanation

This is a release candidate for v195.0.0.
- `@metamask/profile-sync-controller@0.3.0`
- `@metamask/notification-services-controller@0.3.0`

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->

## References

<!--
Are there any issues that this pull request is tied to? Are there other
links that reviewers should consult to understand these changes better?

For example:

* Fixes #12345
* Related to #67890
-->

## Changelog

```md
### Changed

- Bump `@metamask/profile-sync-controller` from `^0.2.1` to `^0.3.0` ([#4643](#4657))
- Bump `@metamask/notification-services-controller` from `^0.2.1` to `^0.3.0` ([#4643](#4657))
```

## Checklist

- [x] I've updated the test suite for new or updated code as appropriate
- [x] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [x] I've highlighted breaking changes using the "BREAKING" category
above as appropriate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants