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

chore: release main #757

Merged
merged 1 commit into from
Jun 25, 2024
Merged

chore: release main #757

merged 1 commit into from
Jun 25, 2024

Conversation

zone-live
Copy link
Collaborator

🤖 I have created a release beep boop

@metamask-institutional/custody-controller: 0.2.30

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @metamask-institutional/custody-keyring bumped from ^2.0.2 to ^2.0.3
      • @metamask-institutional/sdk bumped from ^0.1.29 to ^0.1.30
@metamask-institutional/custody-keyring: 2.0.3

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @metamask-institutional/sdk bumped from ^0.1.29 to ^0.1.30
@metamask-institutional/extension: 0.3.27

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @metamask-institutional/custody-controller bumped from ^0.2.29 to ^0.2.30
      • @metamask-institutional/custody-keyring bumped from ^2.0.2 to ^2.0.3
      • @metamask-institutional/sdk bumped from ^0.1.29 to ^0.1.30
      • @metamask-institutional/transaction-update bumped from ^0.2.4 to ^0.2.5
@metamask-institutional/institutional-features: 1.3.5

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @metamask-institutional/custody-keyring bumped from ^2.0.2 to ^2.0.3
sdk: 0.1.30

0.1.30 (2024-06-25)

Bug Fixes

  • check null values: checking null values in signedMEssage and transaction (#233) (3e21fb9)
  • content-type: setting content-type as json (#494) (c1afa70)
  • errormessage: if the server responds with a 401 status code when trying to get the access token (#534) (593b2a2)
  • fetchapi: error handling with fetch api (#500) (cf64009)
  • lint: lint issues were fixes (#509) (ce5f9af)
  • npmignore: clean up (#271) (a4bbae1)
  • only create an ITR event if the custodian returns a URL where the user can go (#608) (dc17ed2)
  • refresh-token: logic around refresh token (#682) (14b771c)
  • response: response result (#543) (d649bd3)
  • sdk: bump version (#721) (a965fe4)
  • sdk: fetch is not working as axios so we moved our logic outside catch (#140) (b9391aa)
  • sdk: manual publish (#753) (e45b76d)
  • updates packages: updates packages to the latest versions (#278) (0dc78c5)
@metamask-institutional/transaction-update: 0.2.5

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @metamask-institutional/custody-keyring bumped from ^2.0.2 to ^2.0.3
      • @metamask-institutional/sdk bumped from ^0.1.29 to ^0.1.30
      • @metamask-institutional/websocket-client bumped from ^0.2.4 to ^0.2.5
@metamask-institutional/websocket-client: 0.2.5

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @metamask-institutional/custody-keyring bumped from ^2.0.2 to ^2.0.3
      • @metamask-institutional/sdk bumped from ^0.1.29 to ^0.1.30

This PR was generated with Release Please. See documentation.

@zone-live zone-live merged commit bfae0ed into main Jun 25, 2024
6 checks passed
@zone-live zone-live deleted the release-please--branches--main branch June 25, 2024 10:38
@zone-live
Copy link
Collaborator Author

@zone-live
Copy link
Collaborator Author

@zone-live
Copy link
Collaborator Author

@zone-live
Copy link
Collaborator Author

@zone-live
Copy link
Collaborator Author

@zone-live
Copy link
Collaborator Author

@zone-live
Copy link
Collaborator Author

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.

1 participant