[Snyk] Upgrade @stellar/stellar-sdk from 12.1.0 to 12.2.0 #7
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.
Snyk has created this PR to upgrade @stellar/stellar-sdk from 12.1.0 to 12.2.0.
ℹ️ 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 1 version ahead of your current version.
The recommended version was released on a month ago.
Release notes
Package name: @stellar/stellar-sdk
Fixed
@ stellar/stellar-base
and its underlying dependency@ stellar/js-xdr
have been upgraded to their latest versions; reference their release notes (v12.1.0 and v3.1.2, respectively) for details (#1013).Added
rpc.Server
andHorizon.Server
(#1013):const s = new Server("<some URL>", { headers: { "X-Custom-Header": "hello" }})
Horizon.Server
now supports the newPOST /transactions_async
endpoint via thesubmitAsyncTransaction
method (#989). Its purpose is to provide an immediate response to the submission rather than waiting for Horizon to determine its status. The response schema is as follows:rpc.Server
now has agetFeeStats
method which retrieves fee statistics for a previous chunk of ledgers to provide users with a way to provide informed decisions about getting their transactions included in the following ledgers (#998):sorobanInclusionFee: FeeDistribution;
inclusionFee: FeeDistribution;
latestLedger: number; // uint32
}
interface FeeDistribution {
max: string; // uint64
min: string; // uint64
mode: string; // uint64
p10: string; // uint64
p20: string; // uint64
p30: string; // uint64
p40: string; // uint64
p50: string; // uint64
p60: string; // uint64
p70: string; // uint64
p80: string; // uint64
p90: string; // uint64
p95: string; // uint64
p99: string; // uint64
transactionCount: string; // uint32
ledgerCount: number; // uint32
}
New Contributors
Full Changelog: v12.1.0...v12.2.0
v12.1.0
Added
contract
now exports theDEFAULT_TIMEOUT
(#984).contract.AssembledTransaction
now has:toXDR
andfromXDR
methods for serializing the transaction to and from XDR. These methods should be used in place ofAssembledTransaction.toJSON
andAssembledTransaction.fromJSON
for multi-auth signing. The JSON methods are now deprecated. Note: you must now callsimulate
on the transaction before the finalsignAndSend
call after all required signatures are gathered when using the XDR methods (#977).restoreFootprint
method which accepts therestorePreamble
returned when a simulation call fails due to some contract state that has expired. When invoking a contract function, one can now setrestore
totrue
in theMethodOptions
. When enabled, arestoreFootprint
transaction will be created and await signing when required (#991).sign
andsend
methods so that you can sign a transaction without sending it (signAndSend
still works as before; #922).contract.Client
now has atxFromXDR
method which should be used in place oftxFromJSON
for multi-auth signing (#977).Deprecated
contract.AssembledTransaction
,toJSON
andfromJSON
should be replaced withtoXDR
andfromXDR
.contract.Client
,txFromJSON
should be replaced withtxFromXDR
.Fixed
AssembledTransaction
withtx.raw = cloneFrom(tx.build)
, thetx.simulationData
will now be updated correctly (#985).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: