[Snyk] Upgrade @taquito/taquito from 19.2.0 to 19.2.1 #1882
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade @taquito/taquito from 19.2.0 to 19.2.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 4 versions ahead of your current version.
The recommended version was released on 2 months ago.
Release notes
Package name: @taquito/taquito
Summary
New Features
Beacon Migration
As of Beacon version 4.2.0, Beacon have migrated from using
dAppClient.getActiveAccount()
to using an event subscription methodBeaconEvent.ACTIVE_ACCOUNT_SET
for handling active account changes.IF YOU ARE STILL USING THE
eventHandlers
PROPERTY WHEN INITIALIZING A DAPP CLIENT, PLEASE UPDATE YOUR CODE.For a more detailed migration guide, please refer to this document
Internals
@ taquito/beacon-wallet
to usesubscribeToEvent()
instead ofgetActiveAccount()
#2958Summary
New Features
Beacon Migration
As of Beacon version 4.2.0, Beacon have migrated from using
dAppClient.getActiveAccount()
to using an event subscription methodBeaconEvent.ACTIVE_ACCOUNT_SET
for handling active account changes.IF YOU ARE STILL USING THE
eventHandlers
PROPERTY WHEN INITIALIZING A DAPP CLIENT, PLEASE UPDATE YOUR CODE.For a more detailed migration guide, please refer to this document
Summary
New Features
Beacon Migration
As of Beacon version 4.2.0, Beacon have migrated from using
dAppClient.getActiveAccount()
to using an event subscription methodBeaconEvent.ACTIVE_ACCOUNT_SET
for handling active account changes.IF YOU ARE STILL USING THE
eventHandlers
PROPERTY WHEN INITIALIZING A DAPP CLIENT, PLEASE UPDATE YOUR CODE.For a more detailed migration guide, please refer to this document
Summary
Beacon Migration
As of Beacon version 4.2.0, Beacon have migrated from using
dAppClient.getActiveAccount()
to using an event subscription methodBeaconEvent.ACTIVE_ACCOUNT_SET
for handling active account changes.IF YOU ARE STILL USING THE
eventHandlers
PROPERTY WHEN INITIALIZING A DAPP CLIENT, PLEASE UPDATE YOUR CODE.For a more detailed migration guide, please refer to this document
New Features
Documentation
Internals
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: